Gcore incident

Cloud | Sines-3 Incident Details

Minor Resolved

Gcore experienced a minor incident on June 3, 2026 affecting Networking (Sines-3), lasting 20h 31m. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 12:30 AM UTC
Resolved
Jun 03, 2026, 09:01 PM UTC
Duration
20h 31m
Detected by Pingoru
Jun 03, 2026, 12:30 AM UTC

Affected components

Networking (Sines-3)

Update timeline

  1. investigating Jun 03, 2026, 12:30 AM UTC

    We are currently experiencing a partial outage in our network performance in Sines-3 region, which may result in partial unavailability for users. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide updates as soon as more information becomes available on the progress of the resolution. Thank you for your understanding and cooperation.

  2. resolved Jun 03, 2026, 02:51 AM UTC

    This incident has been resolved.

  3. monitoring Jun 03, 2026, 04:17 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. investigating Jun 03, 2026, 06:26 AM UTC

    This is to inform you that the issue with our Cloud service affecting network performance has reoccurred after we previously set it to monitoring following the applied fix. We are resuming our investigation to identify and resolve the root cause as quickly as possible. Customers may continue to experience partial unavailability during this time. We apologize for the ongoing inconvenience and appreciate your patience and understanding. We will provide updates as soon as more information becomes available on the progress of the resolution. Thank you for your understanding and cooperation.

  5. investigating Jun 03, 2026, 03:22 PM UTC

    This is to inform you that we are currently deeply investigating the network issue, and trying to solve the issue with ARP flood in the Sines-3\. Customers may continue to experience partial unavailability during this time. We apologize for the ongoing inconvenience and appreciate your patience and understanding. We will provide updates as soon as more information becomes available on the progress of the resolution. Thank you for your understanding and cooperation.

  6. monitoring Jun 03, 2026, 07:11 PM UTC

    We localized the problem, implemented a fix and are currently monitoring the result.

  7. resolved Jun 03, 2026, 09:01 PM UTC

    This incident has been resolved.