Gcore Outage History

Gcore is up right now

Gcore had 65 outages in the last 2 years totaling 342h 57m of downtime — averaging 2.7 incidents per month.

There were 65 Gcore outages since March 4, 2026 totaling 342h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gcore.com

Minor August 1, 2026

SFTP Storage | Eschborn Incident Details

Detected by Pingoru
Aug 01, 2026, 01:16 PM UTC
Resolved
Aug 04, 2026, 10:03 AM UTC
Duration
2d 20h
Affected: Object Storage (SFTP Eschborn)
Timeline · 4 updates
  1. investigating Aug 01, 2026, 01:16 PM UTC

    We are currently experiencing a partial outage in our SFTP storage, 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. identified Aug 01, 2026, 04:35 PM UTC

    We are continuing to work on a fix for this incident. Our engineering team has identified the cause and is currently implementing a resolution as quick as possible. We will provide regular updates as we receive more information on the progress of the resolution. Thank you for your understanding and cooperation.

  3. monitoring Aug 02, 2026, 11:25 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve the partial outage in our SFTP storage. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  4. resolved Aug 04, 2026, 10:03 AM UTC

    We are happy to inform you that the partial outage in our SFTP storage has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Minor August 1, 2026

Hosting | Global Incident Details

Detected by Pingoru
Aug 01, 2026, 09:23 AM UTC
Resolved
Aug 01, 2026, 03:50 PM UTC
Duration
6h 26m
Affected: Global services (Hosting Portal)
Timeline · 3 updates
  1. investigating Aug 01, 2026, 09:23 AM UTC

    We are currently experiencing a partial outage in our hosting platform, which may result in partial unavailability of the portal 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. monitoring Aug 01, 2026, 10:17 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Aug 01, 2026, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2026

CDN & Hosting | Santiago de Queretaro, Mexico, Incident Details

Detected by Pingoru
Jul 31, 2026, 09:48 PM UTC
Resolved
Aug 01, 2026, 03:12 AM UTC
Duration
5h 24m
Affected: Latin America (Santiago de Querétaro (SQR))Latin America (Santiago de Querétaro, Mexico)
Timeline · 2 updates
  1. investigating Jul 31, 2026, 09:48 PM UTC

    We are currently experiencing a partial outage in our CDN service, which may result in partial unavailability for users. The traffic has been temporarily rerouted. 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 Aug 01, 2026, 03:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 25, 2026

Cloud | Istanbul Incident Details

Detected by Pingoru
Jul 25, 2026, 08:03 PM UTC
Resolved
Jul 27, 2026, 02:13 PM UTC
Duration
1d 18h
Affected: Networking (Istanbul)
Timeline · 3 updates
  1. identified Jul 25, 2026, 08:03 PM UTC

    We are currently experiencing a public network outage affecting Cloud services in Istanbul. Some users may experience network connectivity issues, degraded availability, or temporary unavailability of affected Cloud resources in this location. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this time. Our team is actively working to identify the cause and implement a resolution as quickly as possible. We will provide regular updates as we gather more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. monitoring Jul 26, 2026, 08:19 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 27, 2026, 02:13 PM UTC

    We are happy to inform you that the partial outage affecting Cloud services in Istanbul has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Major July 21, 2026

S3 Storage | Luxembourg Incident Details

Detected by Pingoru
Jul 21, 2026, 07:59 PM UTC
Resolved
Jul 21, 2026, 08:25 PM UTC
Duration
25m
Affected: Object Storage (S3 Luxembourg)
Timeline · 4 updates
  1. investigating Jul 21, 2026, 07:59 PM UTC

    We are currently experiencing a major outage with S3 Storage in Luxembourg , resulting in a complete unavailability of the service. We sincerely apologise for any inconvenience this may cause and greatly appreciate your patience and understanding during this critical time. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide regular updates as we receive more information on the progress of the resolution Thank you for your understanding and cooperation.

  2. identified Jul 21, 2026, 08:07 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Jul 21, 2026, 08:08 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jul 21, 2026, 08:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 17, 2026

Cloud | Chester Incident Details

Detected by Pingoru
Jul 17, 2026, 01:01 AM UTC
Resolved
Jul 18, 2026, 11:30 AM UTC
Duration
1d 10h
Affected: Networking (Chester)
Timeline · 3 updates
  1. investigating Jul 17, 2026, 01:01 AM UTC

    We are currently experiencing a major outage affecting Cloud services in Chester region, resulting in a complete unavailability of the service. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this critical time. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide regular updates as we receive more information on the progress of the resolution Thank you for your understanding and cooperation.

  2. monitoring Jul 17, 2026, 02:05 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve the major outage affecting Cloud services in Chester region. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  3. resolved Jul 18, 2026, 11:30 AM UTC

    We are happy to inform you that the major outage affecting Cloud services in Chester region has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Minor July 14, 2026

Hosting | Paris Incident Details

Detected by Pingoru
Jul 14, 2026, 11:31 AM UTC
Resolved
Jul 17, 2026, 06:01 AM UTC
Duration
2d 18h
Affected: Global services (DCImanager)Europe (Paris (PA5))
Timeline · 3 updates
  1. investigating Jul 14, 2026, 11:31 AM UTC

    We are currently experiencing a partial outage in our Hosting services in Paris ( PA5) , which may result in partial unavailability of the DCI manager 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. monitoring Jul 14, 2026, 06:05 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 17, 2026, 06:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 13, 2026

CDN | Statistics Incident Details

Detected by Pingoru
Jul 13, 2026, 01:45 PM UTC
Resolved
Jul 13, 2026, 04:02 PM UTC
Duration
2h 16m
Affected: Global services (Statistics)
Timeline · 2 updates
  1. investigating Jul 13, 2026, 01:45 PM UTC

    We are currently experiencing a degraded performance in our CDN statistics, which may result in delays in data and can cause smaller data readings. 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 Jul 13, 2026, 04:02 PM UTC

    We are happy to inform you that the degraded performance in our CDN statistics has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Minor July 9, 2026

CDN | Lima, Peru Incident Details

Detected by Pingoru
Jul 09, 2026, 04:59 PM UTC
Resolved
Jul 10, 2026, 06:01 AM UTC
Duration
13h 1m
Affected: Latin America (Lima, Peru)
Timeline · 3 updates
  1. investigating Jul 09, 2026, 04:59 PM UTC

    We are currently experiencing a partial degradation in performance in Lima, Peru , and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. monitoring Jul 09, 2026, 05:23 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 10, 2026, 06:01 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Lima, Peru and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Minor July 9, 2026

Cloud | Baku, Azerbaijan Incident Details

Detected by Pingoru
Jul 09, 2026, 03:01 AM UTC
Resolved
Jul 09, 2026, 05:02 AM UTC
Duration
2h 1m
Affected: Global services (API)Networking (Baku)
Timeline · 2 updates
  1. monitoring Jul 09, 2026, 03:01 AM UTC

    We are currently experiencing performance degradation in our Cloud services in Baku, Azerbaijan, which may result in slow or unusual functioning of our services. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this time. Our team is actively working to identify the cause and implement a resolution as quickly as possible. We will provide regular updates as we gather more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. resolved Jul 09, 2026, 05:02 AM UTC

    We are happy to inform you that the performance degradation in our Cloud services in Baku, Azerbaijan, has been resolved. The exact timeframe is 01:53:17 UTC - 02.11 UTC. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Major July 8, 2026

CDN and Hosting | Atlanta Incident Details

Detected by Pingoru
Jul 08, 2026, 01:54 PM UTC
Resolved
Jul 09, 2026, 03:53 PM UTC
Duration
1d 1h
Affected: North America (Atlanta, United States)North America (Atlanta (ATL2))
Timeline · 3 updates
  1. investigating Jul 08, 2026, 01:54 PM UTC

    We are currently experiencing a major outage in our Hosting services in Atlanta, resulting in a complete unavailability of the service. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this critical time. While in CDN, we are having partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide regular updates as we receive more information on the progress of the resolution Thank you for your understanding and cooperation.

  2. monitoring Jul 08, 2026, 02:52 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 09, 2026, 03:53 PM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Atlanta and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Minor June 30, 2026

Cloud | Luxembourg Incident Details

Detected by Pingoru
Jun 30, 2026, 10:11 AM UTC
Resolved
Jun 30, 2026, 11:22 AM UTC
Duration
1h 10m
Affected: Compute (Luxembourg-2)Networking (Luxembourg-2)
Timeline · 5 updates
  1. investigating Jun 30, 2026, 10:11 AM UTC

    We are currently experiencing a partial outage in our network and compute services in Luxembourg (Luxembourg-2) location, 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. monitoring Jun 30, 2026, 10:29 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve partial outage in Luxembourg location. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  3. identified Jun 30, 2026, 10:45 AM UTC

    We are continuing to work on a fix for this incident.

  4. monitoring Jun 30, 2026, 11:06 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve partial outage in Luxembourg location. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  5. resolved Jun 30, 2026, 11:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 27, 2026

Cloud | Tokyo Incident Details

Detected by Pingoru
Jun 27, 2026, 07:27 AM UTC
Resolved
Jun 27, 2026, 07:46 AM UTC
Duration
18m
Affected: Cloud (Block Storage)
Timeline · 2 updates
  1. investigating Jun 27, 2026, 07:27 AM UTC

    We are currently experiencing performance degradation in our Tokyo servers, which may result in slow or unusual functioning with the disks. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this time. Our team is actively working to identify the cause and implement a resolution as quickly as possible. We will provide regular updates as we gather more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. resolved Jun 27, 2026, 07:46 AM UTC

    We are happy to inform you that the partial outage in our Tokyo region has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Minor June 26, 2026

All Services | Global Service Degradation Retrospective Incident Details

Detected by Pingoru
Jun 26, 2026, 11:20 AM UTC
Resolved
Jun 26, 2026, 11:20 AM UTC
Duration
Affected: Gcore Systems (Global Degradation)
Timeline · 2 updates
  1. resolved Jun 26, 2026, 11:20 AM UTC

    We would like to inform you that between 11:20 UTC 26/June/2026 and 11:25 UTC 26/June/2026, our engineers observed a degradation in our Services. However, our team took swift action to resolve the issue, and we are pleased to confirm that the degradation issue is now resolved. We apologize for any inconvenience this may have caused you and appreciate your patience and understanding during this time. If you are still experiencing any issues, please do not hesitate to contact our support team by opening a ticket. Our team will be happy to assist you in any way possible. Thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

  2. resolved Jun 26, 2026, 11:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2026

All services | Miami Incident Details

Detected by Pingoru
Jun 23, 2026, 10:39 PM UTC
Resolved
Jun 24, 2026, 12:08 AM UTC
Duration
1h 29m
Affected: Object Storage (SFTP Miami)North America (Miami, United States)North America (Miami (MI2))
Timeline · 3 updates
  1. investigating Jun 23, 2026, 10:39 PM UTC

    We are currently experiencing a major outage in the Miami region for all services, resulting in complete unavailability of the service. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this critical time. Our engineering team is actively working to identify the root cause and implement a resolution as quickly as possible. We will provide regular updates as we receive more information on the progress of the resolution Thank you for your understanding and cooperation.

  2. monitoring Jun 23, 2026, 11:15 PM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve the major outage in all services in the Miami region. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  3. resolved Jun 24, 2026, 12:08 AM UTC

    We are happy to inform you that the major outage in the Miami region for all services has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

Read the full incident report →

Minor June 23, 2026

CDN | Ashburn Incident Details

Detected by Pingoru
Jun 23, 2026, 09:58 AM UTC
Resolved
Jun 23, 2026, 11:41 AM UTC
Duration
1h 42m
Affected: North America (Ashburn, United States)
Timeline · 3 updates
  1. investigating Jun 23, 2026, 09:58 AM UTC

    We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. monitoring Jun 23, 2026, 10:35 AM UTC

    We are pleased to inform you that our engineering team has successfully rerouted the traffic back to Ashburn. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have confirmed that everything is completely resolved.

  3. resolved Jun 23, 2026, 11:41 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Ashburn and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Major June 20, 2026

CDN | Chile Incident Details

Detected by Pingoru
Jun 20, 2026, 11:22 AM UTC
Resolved
Jun 20, 2026, 11:40 AM UTC
Duration
17m
Affected: Latin America (Santiago de Chile, Chile)
Timeline · 1 update
  1. investigating Jun 20, 2026, 11:22 AM UTC

    We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

Read the full incident report →

Major June 20, 2026

CDN and Hosting| Hungary Incident Details

Detected by Pingoru
Jun 20, 2026, 05:33 AM UTC
Resolved
Jun 20, 2026, 06:27 AM UTC
Duration
53m
Affected: Global services (Advanced Analytics)Global services (API)Global services (Configuration Deployment)Global services (Content Delivery)Global services (Customer Portal)Global services (Image Stack)Global services (Log Viewer)Global services (Origin Shielding)Global services (Prefetch)Global services (Purge)Global services (Statistics)Europe (Budapest (BIX))Global services (Logs Uploader)
Timeline · 1 update
  1. investigating Jun 20, 2026, 05:33 AM UTC

    We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

Read the full incident report →

Minor June 18, 2026

CDN | Jakarta Incident Details

Detected by Pingoru
Jun 18, 2026, 06:27 AM UTC
Resolved
Jun 18, 2026, 10:35 AM UTC
Duration
4h 8m
Affected: Asia & Pacific (Jakarta, Indonesia)
Timeline · 2 updates
  1. investigating Jun 18, 2026, 06:27 AM UTC

    We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. resolved Jun 18, 2026, 10:35 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Jakarta and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Minor June 17, 2026

CDN | Athens Incident Details

Detected by Pingoru
Jun 17, 2026, 12:44 PM UTC
Resolved
Jun 18, 2026, 11:08 AM UTC
Duration
22h 23m
Affected: Europe (Athens, Greece)
Timeline · 3 updates
  1. investigating Jun 17, 2026, 12:44 PM UTC

    We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. identified Jun 17, 2026, 09:07 PM UTC

    We are continuing to work on a fix for this incident.

  3. resolved Jun 18, 2026, 11:08 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Athens and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Notice June 11, 2026

CDN | Singapore, Amsterdam Retrospective Incident Details

Detected by Pingoru
Jun 11, 2026, 01:30 AM UTC
Resolved
Jun 11, 2026, 01:30 AM UTC
Duration
Affected: Europe (Amsterdam, Netherlands)Asia & Pacific (Singapore)
Timeline · 2 updates
  1. resolved Jun 11, 2026, 01:30 AM UTC

    We would like to inform you that between 01:33 UTC 11/06/26 and 01:48 UTC 11/06/26, our engineers observed a degradation in CDN. However, our team took swift action to resolve the issue, and we are pleased to confirm that the CDN Partial Outage issue is now resolved. We apologize for any inconvenience this may have caused you and appreciate your patience and understanding during this time. If you are still experiencing any issues, please do not hesitate to contact our support team by opening a ticket. Our team will be happy to assist you in any way possible. Thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])

  2. resolved Jun 11, 2026, 02:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

CDN | El Paso Incident Details

Detected by Pingoru
Jun 10, 2026, 05:17 PM UTC
Resolved
Jun 11, 2026, 07:47 AM UTC
Duration
14h 29m
Affected: North America (El Paso, United States)
Timeline · 3 updates
  1. investigating Jun 10, 2026, 05:17 PM UTC

    We are currently experiencing a major outage, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will provide an update as soon as we have more information on the progress of the resolution. Thank you for your understanding and cooperation.

  2. identified Jun 11, 2026, 01:27 AM UTC

    We are continuing to work on a fix for this incident.

  3. resolved Jun 11, 2026, 07:47 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to El Paso and has returned to normal operations. Should you experience any issues, please feel free to contact our support team, who are ready to assist you and address any queries promptly. Thank you for your patience and understanding during this time. We truly appreciate your cooperation. For further assistance, please reach out to our support team at [**[email protected]**](mailto:[email protected]).

Read the full incident report →

Major June 4, 2026

All Services| Almaty Incident Details

Detected by Pingoru
Jun 04, 2026, 10:37 PM UTC
Resolved
Jun 05, 2026, 06:39 AM UTC
Duration
8h 1m
Affected: Compute (Almaty)Global services (Advanced Analytics)Baremetal (Almaty)Compute (Amsterdam)Global services (API)Networking (Almaty)Baremetal (Amsterdam)Compute (Baku)Africa (Addis Ababa, Ethiopia)Africa (Abidjan, Côte d’Ivoire)Asia & Pacific (Almaty, Kazakhstan)Global services (API)Global services (Configuration Deployment)Baremetal (Chester)Networking (Amsterdam)Compute (Chester)Global services (Quota Management)Compute (Chicago)Networking (Baku)Basic VM (Almaty)Asia & Pacific (Astana, Kazakhstan)Global services (Content Delivery)Baremetal (Chicago)Europe (Amsterdam, Netherlands)Africa (Bamako, Mali)Managed Kubernetes (Almaty)Global services (Customer Portal)Africa (Cairo, Egypt)Basic VM (Amsterdam)Asia & Pacific (Baku (AZT), Azerbaijan)Networking (Chester)Global services (Customer Portal)Baremetal (Dubai)Europe (Athens, Greece)Compute (Darmstadt)Middle East (Amman, Jordan)Europe (Belgrade, Serbia)Compute (Dubai)Basic VM (Chicago)Cloud (Block Storage)North America (Ashburn, United States)Networking (Chicago)Africa (Cape Town, South Africa)Managed Kubernetes (Amsterdam)Global services (Image Stack)Middle East (Baghdad, Iraq)Asia & Pacific (Baku (GYD), Azerbaijan)Baremetal (Frankfurt am Main)Global services (API)Compute (Frankfurt am Main)Global services (Log Viewer)Baremetal (Frankfurt-2)Basic VM (Dubai)Managed Kubernetes (Chester)Networking (Darmstadt)North America (Atlanta, United States)Latin America (Alto Parana, Paraguay)Asia & Pacific (Bishkek, Kyrgyzstan)Europe (Bratislava, Slovakia)Africa (Casablanca, Morocco)Middle East (Doha, Qatar)Cloud (Containers)Cloud (Database)Global services (Billing System)Compute (Frankfurt-2)North America (Boston, United States)Baremetal (Helsinki)Global services (Origin Shielding)Europe (Brussels, Belgium)Asia & Pacific (Bangkok, Thailand)Asia, Oceania, and Africa (Almaty (KAL))Middle East (Dubai, United Arab Emirates)Latin America (Asunción, Paraguay)Managed Kubernetes (Chicago)Basic VM (Frankfurt am Main)Networking (Dubai)Africa (Douala, Cameroon)Africa (Harare, Zimbabwe)Object Storage (API)Middle East (Erbil, Iraq)Global services (Prefetch)Managed Kubernetes (Darmstadt)Cloud (File Shares as a Service)Europe (Amsterdam (AM3))Latin America (Bogota, Colombia)Asia & Pacific (Colombo, Sri Lanka)Networking (Frankfurt am Main)North America (Chicago (CCH1), United States)Baremetal (Hong Kong)Compute (Helsinki)Asia, Oceania, and Africa (Baku (DTA))Basic VM (Hong Kong)Europe (Bucharest, Romania)Global services (Hosting Portal)Latin America (Buenos Aires, Argentina)Cloud (Function as a Service)Global services (DNS Service & Portal)Managed Kubernetes (Dubai)Compute (Hong Kong)Global services (Purge)Networking (Frankfurt-2)Europe (Amsterdam (DRA4))Baremetal (Incheon)North America (Ashburn (DC11))Middle East (Istanbul, Turkey)Asia, Oceania, and Africa (Hong Kong (GNC))North America (Chicago (DRC), United States)Europe (Budapest, Hungary)Object Storage (Customer Portal)Basic VM (Istanbul)Asia & Pacific (Davao, Philippines)Africa (Johannesburg, South Africa)Middle East (Kuwait City, Kuwait)Basic VM (London)Africa (Kampala, Uganda)Global services (Statistics)Managed Kubernetes (Frankfurt am Main)Global services (DCImanager)North America (Dallas, United States)Asia, Oceania, and Africa (Istanbul (TII))Europe (Bucharest (BU2))North America (Ashburn (ANX))Compute (Incheon)Baremetal (Istanbul)Object Storage (S3 Chicago)Asia & Pacific (Dhaka, Bangladesh)Europe (Chișinău, Moldova)Latin America (Caracas, Venezeula)Networking (Helsinki)Latin America (Fortaleza (FLZ))Cloud (Managed Logging)Europe (Dublin, Ireland)North America (Denver, United States)Asia & Pacific (Duschanbe, Tajikistan)Cloud (Managed PostgreSQL)Middle East (Manama, Bahrain)Baremetal (Johannesburg)Basic VM (Luxembourg)Compute (Istanbul)Latin America (Fortaleza, Brazil)Africa (Kinshasa, Congo)Global services (VMmanager)Asia, Oceania, and Africa (Johannesburg (JB1))Object Storage (S3 Darmstadt)Networking (Hong Kong)Latin America (Lima (LLP))Europe (Budapest (BIX))Managed Kubernetes (Frankfurt-2)North America (Atlanta (ATL2))Latin America (Santiago de Querétaro (SQR))Networking (Incheon)North America (Chicago (CH1))Managed Kubernetes (Hong Kong)Europe (Chișinău (MLT))Object Storage (S3 Luxembourg)Basic VM (Manassas)Africa (Lagos, Nigeria)Latin America (Guatemala City, Guatemala)North America (El Paso, United States)Asia & Pacific (Hanoi, Vietnam)Cloud (Registry)Asia, Oceania, and Africa (Melbourne (MDC))Europe (Frankfurt, Germany)Baremetal (London)Middle East (Muscat, Oman)Compute (Johannesburg)Basic VM (Mumbai)Europe (Helsinki, Finland)North America (Chicago (DRC))Europe (Frankfurt (DRF))Latin America (São Paulo (SP3))Middle East (Riyadh, Saudi Arabia)Latin America (Guayaquil, Ecuador)Africa (Lome, Togo)Object Storage (S3 Singapore)London-2Asia, Oceania, and Africa (Mumbai (WW))Asia & Pacific (Ho Chi Minh City, Vietnam)Networking (Johannesburg)Compute (London)Managed Kubernetes (Istanbul)North America (Los Angeles, United States)Africa (Luanda, Angola)North America (Manassas, United States)Latin America (Lima, Peru)Baremetal (Luxembourg)Europe (Kharkiv, Ukraine)North America (Los Angeles (LA2))Asia & Pacific (Hong Kong)Europe (Kyiv (GN))Networking (Istanbul)Managed Kubernetes (London)Asia, Oceania, and Africa (Seoul (KX))Object Storage (SFTP Amsterdam)London-2Middle East (Sana’a, Yemen)Basic VM (Singapore)Object Storage (SFTP Frankfurt)Basic VM (São Paulo-2)Middle East (Tel Aviv, Israel)Asia & Pacific (Jakarta, Indonesia)Baremetal (Luxembourg-2)Latin America (Maracaibo, Venezuela)Europe (London (TL))Networking (London)Asia, Oceania, and Africa (Singapore (SGC))North America (McAllen, United States)Compute (Luxembourg)North America (Miami (MI1))Africa (Lusaka, Zambia)Europe (Kyiv, Ukraine)Managed Kubernetes (Luxembourg-2)Asia, Oceania, and Africa (Singapore (SG2))Asia & Pacific (Karaganda, Kazakhstan)London-2Africa (Mombasa, Kenya )Managed Kubernetes (Luxembourg-3)Object Storage (SFTP Miami)Compute (Luxembourg-2)Europe (Lille, France)Basic VM (Tashkent)North America (Miami, United States)Baremetal (Luxembourg-3)North America (Miami (MI2))Europe (London (LD3))Latin America (Panama City, Panama)Networking (Luxembourg)North America (Minneapolis (MIN4))Baremetal (Manassas)Asia, Oceania, and Africa (Sydney (SY4))Europe (Luxembourg (ED))Managed Kubernetes (Manassas)Asia & Pacific (Kathmandu, Nepal)Latin America (Porto Alegre, Brazil)Africa (Nairobi, Kenya)Europe (Lisbon, Portugal)Compute (Luxembourg-3)Basic VM (Tokyo)North America (Minneapolis, United States)Asia, Oceania, and Africa (Tel Aviv (BZI))Africa (Ouagadougou, Burkina Faso)Europe (Madrid (CM))Compute (Manassas)Baremetal (Mumbai)Latin America (Quito, Ecuador)Asia & Pacific (Manila, Philippines)North America (New York, United States)Networking (Luxembourg-2)Managed Kubernetes (Paris-2)North America (New York (NY2))Europe (London, United Kingdom)Africa (Rabat, Morocco)Baremetal (Paris-2)Managed Kubernetes (São Paulo-2)Europe (Milan (ML2))Asia, Oceania, and Africa (Tokyo (CC1))Networking (Luxembourg-3)North America (San Jose, United States)North America (Santa Clara (SCL2))Compute (Mumbai)Europe (Luxembourg)Asia & Pacific (Mumbai, India)Latin America (Rio de Janeiro, Brazil)Compute (Paris-2)Asia & Pacific (Melbourne, Australia)North America (Seattle, United States)Europe (Lviv, Ukraine)Latin America (San José, Costa Rica)Baremetal (Santa Clara)Asia, Oceania, and Africa (Yerevan (UCOM))Europe (Paris (PA5))Networking (Manassas)Managed Kubernetes (Sines-2)Africa (Rose Belle, Mauritius)Europe (Lyon, France)Asia & Pacific (Osaka, Japan)Europe (Sofia (TSC))Networking (Mumbai)Africa (Saint-Denis, France)Managed Kubernetes (Sines-3)Compute (Santa Clara)North America (Toronto, Canada)Latin America (San Salvador, El Salvador)Baremetal (São Paulo)Managed Kubernetes (Singapore)Africa (Tripoli, Libya)Compute (São Paulo)Europe (Madrid, Spain)Latin America ( Santa Cruz de la sierra, Bolivia)Asia & Pacific (Pavlodar, Kazakhstan)Baremetal (São Paulo-2)Europe (Warsaw (PL1))Networking (Paris-2)Compute (São Paulo-2)Networking (Santa Clara)Asia & Pacific (Phnom Penh, Cambodia)Managed Kubernetes (Tokyo-1)Baremetal (Sines-2)Europe (Manchester, United Kingdom)Africa (Windhoek, Namibia)Latin America (Santiago de Chile, Chile)Compute (Sines-2)Asia & Pacific (Seoul, South Korea)Latin America (Santiago de Querétaro, Mexico)Networking (São Paulo)Managed Kubernetes (Warsaw)Europe (Marseille, France)Baremetal (Singapore)Compute (Sines-3)Latin America (São Paulo, Brazil)Asia & Pacific (Shymkent, Kazakhstan)Managed Kubernetes (Santa Clara)Networking (São Paulo-2)Europe (Milan, Italy)Baremetal (Sydney)Networking (Sines-2)Baremetal (Tashkent)Europe (Munich, Germany)Asia & Pacific (Singapore)Compute (Singapore)Latin America (Tegucigalpa, Honduras)Managed Kubernetes (London-2)Europe (Nicosia, Cyprus)Baremetal (Tokyo)Asia & Pacific (Sydney, Australia)Networking (Sines-3)Compute (Tashkent)Compute (Tokyo)SingaporeBaremetal (Warsaw)Europe (Oslo, Norway)Asia & Pacific (Tashkent, Uzbekistan)Europe (Palermo, Italy)Asia & Pacific (Thimphu, Bhutan)Networking (Sydney)Compute (Sydney)Asia & Pacific (Tokyo, Japan)Compute (Warsaw)Networking (Tashkent)Europe (Paris, France)Networking (Tokyo)Europe (Poitiers, France)Asia & Pacific (Ulaanbaatar, Mongolia)Asia & Pacific (Wellington, New Zealand)Networking (Warsaw)Europe (Prague, Czech Republic)Europe (Riga, Latvia)Asia & Pacific (Yangon, Myanmar)Asia & Pacific (Yerevan, Armenia)Europe (Sofia, Bulgaria)Europe (Stockholm, Sweden)Europe (Strasbourg, France)Europe (Tbilisi, Georgia)Europe (Vilnius, Lithuania)Europe (Warsaw, Poland)Europe (Zurich, Switzerland)Managed Kubernetes (Incheon)Africa (Freetown, Sierra Leone)Africa (Cidade de Maputo, Mozambique)Object Storage (S3 Almaty)
Timeline · 7 updates

Read the full incident report →

Minor June 3, 2026

Cloud | Sines-3 Incident Details

Detected by Pingoru
Jun 03, 2026, 12:30 AM UTC
Resolved
Jun 03, 2026, 09:01 PM UTC
Duration
20h 31m
Affected: Networking (Sines-3)
Timeline · 7 updates
  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.

Read the full incident report →