Gcore Outage History

Gcore degraded · 1 active incident View live status →

Gcore had 48 outages in the last 2 years totaling 341h 55m of downtime — averaging 2 incidents per month.

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

Source: https://status.gcore.com

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)Baremetal (London-2)Asia, 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)Compute (London-2)Middle 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)Networking (London-2)Africa (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)Networking (Singapore)Baremetal (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 →

Minor June 2, 2026

Cloud | Multiple regions Incident Details

Detected by Pingoru
Jun 02, 2026, 07:29 AM UTC
Resolved
Jun 02, 2026, 08:34 AM UTC
Duration
1h 4m
Affected: Compute (Baku)Compute (Tashkent)Compute (Sydney)
Timeline · 2 updates
  1. investigating Jun 02, 2026, 07:29 AM UTC

    Our engineering team is currently conducting maintenance on our Cloud service, involving authorization and access to projects. This maintenance will take place on 2026-06-02 during the following time windows: Tashkent: 07:00–07:30 (UTC) Sydney: 07:30–08:00 (UTC) Baku: 08:00–08:30 (UTC) Each time window may include up to 5 minutes of brief service unavailability. During these periods, users may experience short-term disruptions to the project list, projects, and authorization services, as well as potential network connectivity issues or increased delays. We apologize for any inconvenience this may cause 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.

  2. resolved Jun 02, 2026, 08:34 AM UTC

    We are happy to inform you that the unavailability in our Cloud 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 May 30, 2026

Streaming & S3 Storage | Luxemburg Incident Details

Detected by Pingoru
May 30, 2026, 09:48 PM UTC
Resolved
May 31, 2026, 09:04 AM UTC
Duration
11h 15m
Affected: Object Storage (S3 Luxembourg)Streaming (Live Streaming)
Timeline · 3 updates
  1. investigating May 30, 2026, 09:48 PM UTC

    We are currently experiencing a partial outage in our Streaming and S3 Storage in Luxembourg, 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 May 30, 2026, 11:33 PM UTC

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

  3. resolved May 31, 2026, 09:04 AM UTC

    We are happy to inform you that a partial outage in our Streaming and S3 Storage in Luxembourg 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 May 29, 2026

Cloud | Sines Incident Details

Detected by Pingoru
May 29, 2026, 08:26 PM UTC
Resolved
May 29, 2026, 10:57 PM UTC
Duration
2h 31m
Affected: Networking (Sines-2)Networking (Sines-3)
Timeline · 3 updates
  1. investigating May 29, 2026, 08:26 PM UTC

    We are currently experiencing performance degradation in our Network performance in Sines region, 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. monitoring May 29, 2026, 10:41 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 29, 2026, 10:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 28, 2026

DDoS Protection | Global Retrospective Incident Details

Detected by Pingoru
May 28, 2026, 08:40 AM UTC
Resolved
May 28, 2026, 08:40 AM UTC
Duration
Affected: DDoS Protection (Protection)
Timeline · 2 updates
  1. resolved May 28, 2026, 07:40 AM UTC

    We would like to inform you that between 08:40 UTC and 09:40 UTC on May 28, 2026, our engineers observed a degradation affecting all DDoS customers, resulting in a temporary loss of traffic. The impact duration was approximately **one minute** per location, distributed over time and across all affected customers. Our team took swift action to address the issue and is pleased to confirm that the traffic disruption was quickly resolved. We apologize for any inconvenience this may have caused 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 May 28, 2026, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 26, 2026

Colocation | Miami Incident Details

Detected by Pingoru
May 26, 2026, 04:38 AM UTC
Resolved
May 26, 2026, 05:20 AM UTC
Duration
42m
Affected: Colocation (Miami (ICMI))
Timeline · 2 updates
  1. investigating May 26, 2026, 04:38 AM UTC

    We are currently experiencing a major outage in our Network, 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. resolved May 26, 2026, 05:20 AM UTC

    We want to follow up and correct our earlier message. While initial notifications indicated a major outage, the current impact is limited in scope. We apologize for the misleading communication and any unnecessary concern it may have caused. Service is fully operational. Thank you for understanding.

Read the full incident report →

Major May 25, 2026

Hosting | Madrid Incident Details

Detected by Pingoru
May 25, 2026, 11:22 PM UTC
Resolved
May 26, 2026, 09:50 AM UTC
Duration
10h 27m
Affected: Europe (Madrid (CM))
Timeline · 3 updates
  1. investigating May 25, 2026, 11:22 PM UTC

    We are currently experiencing a major outage in our CM Madrid is Down, Hosting impacted, 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 May 26, 2026, 01:20 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 26, 2026, 09:50 AM UTC

    We are happy to inform you that the outage in Madrid 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 May 22, 2026

Network | Mumbai. Incident Details

Detected by Pingoru
May 22, 2026, 08:32 PM UTC
Resolved
May 23, 2026, 05:17 PM UTC
Duration
20h 44m
Affected: Global services (API)Basic VM (Mumbai)Baremetal (Mumbai)Compute (Mumbai)Networking (Mumbai)
Timeline · 3 updates
  1. investigating May 22, 2026, 08:32 PM UTC

    We are currently experiencing performance degradation in our connectivity to the cloud compute inside the region from outside the region (Mumbai), 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. monitoring May 22, 2026, 09:49 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 23, 2026, 05:17 PM UTC

    We are happy to inform you that the performance degradation in connectivity to cloud compute in the 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 May 19, 2026

DDoS Protection | Statistics Incident Details

Detected by Pingoru
May 19, 2026, 11:46 AM UTC
Resolved
May 19, 2026, 12:33 PM UTC
Duration
47m
Affected: Gcore Systems (Customer Portal)DDoS Protection (Statistics)
Timeline · 3 updates
  1. investigating May 19, 2026, 11:46 AM UTC

    We are currently experiencing a partial outage in our DDoS Protection Statistics, 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 May 19, 2026, 11:49 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve partial outage in our DDoS Protection Statistics. 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 May 19, 2026, 12:33 PM UTC

    We are happy to inform you that the partial outage affecting DDoS Protection 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 May 19, 2026

Cloud | Luxembourg Incident Details

Detected by Pingoru
May 19, 2026, 07:08 AM UTC
Resolved
May 19, 2026, 10:40 AM UTC
Duration
3h 31m
Affected: Cloud (Block Storage)Cloud (Function as a Service)Managed Kubernetes (Luxembourg-2)Compute (Luxembourg-2)Networking (Luxembourg-2)Cloud (Load Balancer)
Timeline · 3 updates
  1. investigating May 19, 2026, 07:08 AM UTC

    We are currently experiencing a partial outage in our Cloud Services, 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. Affected Services: Compute, Block Storage (Standard and High IOPS), Load Balancers, and Managed Kubernetes. 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 May 19, 2026, 09:30 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve the partial outage affecting our Cloud Services. However, we are still closely monitoring the situation to ensure stable performance. Affected services include Compute, Block Storage (Standard and High IOPS), Load Balancers, and Managed Kubernetes. We will provide you with an update as soon as we have confirmed that the issue has been completely resolved.

  3. resolved May 19, 2026, 10:40 AM UTC

    We are happy to inform you that the partial outage in our Cloud Services at Luxembourg-2 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. Affected Services: Compute, Block Storage (Standard and High IOPS), Load Balancers, and Managed Kubernetes. 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 May 17, 2026

Cloud | Tokyo Incident Details

Detected by Pingoru
May 17, 2026, 02:33 PM UTC
Resolved
May 17, 2026, 04:35 PM UTC
Duration
2h 2m
Affected: Networking (Tokyo)
Timeline · 3 updates
  1. investigating May 17, 2026, 02:33 PM UTC

    We are currently experiencing an outage in our Tokyo region with our networking services, resulting in a partial unavailability. 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 May 17, 2026, 03:16 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 17, 2026, 04:35 PM UTC

    We are happy to inform you that the outage in Tokyo region with our networking 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 May 15, 2026

Website | Global Incident Details

Detected by Pingoru
May 15, 2026, 07:38 AM UTC
Resolved
May 15, 2026, 11:02 AM UTC
Duration
3h 24m
Affected: Gcore Systems (Website)
Timeline · 4 updates
  1. investigating May 15, 2026, 07:38 AM UTC

    We are currently experiencing a partial outage in our [gcore.com](http://gcore.com) website, 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 May 15, 2026, 08:05 AM UTC

    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 May 15, 2026, 09:10 AM UTC

    We are pleased to inform you that our engineering team has implemented a fix to resolve partial outage in our [**gcore.com**](http://gcore.com) website. 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 May 15, 2026, 11:02 AM UTC

    We are happy to inform you that the partial outage in our [**gcore.com**](http://gcore.com) website 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 May 14, 2026

Hosting | Madrid Incident Details

Detected by Pingoru
May 14, 2026, 02:41 PM UTC
Resolved
May 18, 2026, 06:18 AM UTC
Duration
3d 15h
Affected: Global services (DCImanager)Europe (Madrid (CM))
Timeline · 3 updates
  1. investigating May 14, 2026, 02:41 PM UTC

    We are currently experiencing unavailability in our Madrid DCI6 platform, which may result in location unavailability for the new orders, without affecting the existing client servers. 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 May 15, 2026, 08:05 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 18, 2026, 06:18 AM UTC

    We are happy to inform you that the unavailability in our Madrid DCI6 platform 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 May 13, 2026

Global CDN and API Incident Details

Detected by Pingoru
May 13, 2026, 07:24 PM UTC
Resolved
May 14, 2026, 08:41 AM UTC
Duration
13h 17m
Affected: Gcore Systems (API)Gcore Systems (Billing System)Global services (API)Global services (API)Gcore Systems (Customer Portal)Global services (Content Delivery)Global services (Customer Portal)Global services (Customer Portal)Global services (API)Managed DNS (API)Gcore Systems (Website)
Timeline · 7 updates
  1. investigating May 13, 2026, 07:24 PM UTC

    We are currently experiencing a major outage with our website [gcore.com](http://gcore.com) and Global CDN Delivery, resulting in its complete unavailability. 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 May 13, 2026, 08:05 PM UTC

    The API access has been recovered, and we are continuing to fix other services. We will keep you updated.

  3. identified May 13, 2026, 08:15 PM UTC

    Website and Customer Portal are up again. We are continuing to fix other services.

  4. identified May 13, 2026, 08:23 PM UTC

    We are recovering, and all services are up and running. CDN service has mostly recovered; however, it may still be partially unavailable for some users. We are continuing to monitor the situation and working on the fix.

  5. monitoring May 13, 2026, 08:27 PM UTC

    The issue has been resolved, and all services have fully recovered. We are continuing to monitor the situation to ensure stability. We apologise for the inconvenience.

  6. resolved May 14, 2026, 08:41 AM UTC

    We are happy to inform you that the Major outage with our website, Global CDN Delivery, API access for all services and Customer Portal 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 will also provide a detailed Root Cause Analysis (RCA) once it becomes available. 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])

  7. resolved May 15, 2026, 07:32 PM UTC

    $36

Read the full incident report →

Minor May 13, 2026

Hosting | Kiev Incident Details

Detected by Pingoru
May 13, 2026, 03:25 PM UTC
Resolved
May 14, 2026, 05:53 AM UTC
Duration
14h 28m
Affected: Europe (Kyiv (GN))
Timeline · 3 updates
  1. investigating May 13, 2026, 03:25 PM UTC

    We are currently experiencing a partial outage in our Hosting service in Kiev, which may result in partial unavailability for new orders, without affecting existing clients' servers. 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 May 13, 2026, 11:46 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 14, 2026, 05:53 AM UTC

    We are happy to inform you that the partial unavailability in in our Hosting service in Kiev 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 May 13, 2026

Hosting | Miami Incident Details

Detected by Pingoru
May 13, 2026, 10:56 AM UTC
Resolved
May 18, 2026, 08:07 AM UTC
Duration
4d 21h
Affected: Global services (DCImanager)North America (Miami (MI2))
Timeline · 5 updates
  1. investigating May 13, 2026, 10:56 AM UTC

    We are currently experiencing performance degradation in our Miami - MI2 location, where DCI6 panel is not working, 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. identified May 13, 2026, 12:48 PM UTC

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

  3. identified May 14, 2026, 09:23 AM UTC

    Maintenance is still ongoing. DCI panel in Miami location is accessible now, however there might be temporary issues with OS reinstallation. 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.

  4. monitoring May 15, 2026, 12:00 AM UTC

    We implemented a fix and are currently monitoring the result.

  5. resolved May 18, 2026, 08:07 AM UTC

    We are happy to inform you that the performance degradation in our Miami - MI2 location, where DCI6 panel was not working 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 May 12, 2026

CDN | Istanbul Incident Details

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 10:00 AM UTC
Duration
1h 11m
Affected: Middle East (Amman, Jordan)Middle East (Baghdad, Iraq)Middle East (Doha, Qatar)Middle East (Dubai, United Arab Emirates)Middle East (Erbil, Iraq)Middle East (Istanbul, Turkey)Middle East (Kuwait City, Kuwait)Middle East (Manama, Bahrain)Middle East (Muscat, Oman)Middle East (Riyadh, Saudi Arabia)Middle East (Sana’a, Yemen)Middle East (Tel Aviv, Israel)
Timeline · 3 updates
  1. investigating May 12, 2026, 08:49 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 May 12, 2026, 09:22 AM UTC

    We are pleased to inform you that our engineering team has successfully rerouted the traffic back to Istanbul. 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 May 12, 2026, 10:00 AM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Istanbul 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 May 11, 2026

Hosting | Hosting Portal Incident Details

Detected by Pingoru
May 11, 2026, 11:02 AM UTC
Resolved
May 11, 2026, 11:16 AM UTC
Duration
14m
Affected: Global services (Hosting Portal)
Timeline · 2 updates
  1. monitoring May 11, 2026, 11:02 AM UTC

    We would like to inform you that a partial outage in our hosting service occurred recently. Our engineers took swift action, and we are pleased to confirm that the login issue has now been resolved. We continue to closely monitor the situation to ensure stable performance. We will keep you informed should there be any further updates.

  2. resolved May 11, 2026, 11:16 AM UTC

    We are happy to inform you that the partial outage in our Hosting service 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 May 7, 2026

CDN | Multiple regions Incident Details

Detected by Pingoru
May 07, 2026, 12:41 PM UTC
Resolved
May 07, 2026, 05:25 PM UTC
Duration
4h 44m
Affected: Europe (Lisbon, Portugal)
Timeline · 4 updates
  1. investigating May 07, 2026, 12:41 PM UTC

    We are currently experiencing a partial degradation in performance in Lisbon, Seville, Malaga, Granada and Rocamora, 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 May 07, 2026, 01:37 PM UTC

    We are currently experiencing a partial degradation in performance in Lisbon, Seville, Malaga, Granada, and Rocamora, 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.

  3. identified May 07, 2026, 01:37 PM UTC

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

  4. resolved May 07, 2026, 05:25 PM UTC

    We are happy to inform you that traffic has been successfully rerouted back to Lisbon, Seville, Malaga, Granada, and Rocamora 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 April 30, 2026

CDN | Santiago de Querétaro Retrospective Incident Details

Detected by Pingoru
Apr 30, 2026, 04:05 AM UTC
Resolved
Apr 30, 2026, 04:05 AM UTC
Duration
Affected: Latin America (Santiago de Querétaro, Mexico)
Timeline · 2 updates
  1. resolved Apr 30, 2026, 04:05 AM UTC

    We would like to inform you that between 04:05 UTC 30/04/2026 and 04:21 UTC 30/04/2026, 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 Apr 30, 2026, 04:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Cloud | Luxembourg-3 Incident Details

Detected by Pingoru
Apr 29, 2026, 08:29 AM UTC
Resolved
Apr 29, 2026, 10:00 AM UTC
Duration
1h 31m
Affected: Baremetal (Luxembourg-3)Compute (Luxembourg-3)Networking (Luxembourg-3)
Timeline · 2 updates
  1. investigating Apr 29, 2026, 08:29 AM UTC

    During this time period, our engineering team will be performing scheduled infrastructure upgrades on the Cloud service, which may result in the network unavailability of Cloud service instances (VM, Baremetal, Load Balancer, floating IP, router) for up to **10** min per service instance. We are undertaking these measures to enhance the overall reliability and stability of the service. While we aim to minimize disruption, you may experience brief service interruptions during this maintenance. We appreciate your understanding and patience and sincerely apologize for any inconvenience this may cause. Your satisfaction and the smooth operation of our services remain our top priority. For further information or assistance, please do not hesitate to contact our support team via [**[email protected]**](mailto:[email protected])

  2. resolved Apr 29, 2026, 10:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Cloud | Incheon Incident Details

Detected by Pingoru
Apr 27, 2026, 08:00 AM UTC
Resolved
Apr 27, 2026, 10:04 AM UTC
Duration
2h 3m
Affected: GcoreBaremetal (Incheon)Compute (Incheon)Networking (Incheon)
Timeline · 2 updates
  1. investigating Apr 27, 2026, 08:00 AM UTC

    We are currently experiencing a partial outage in our Cloud service, which may result in partial unavailability of the network and unavailability of Cloud service instances (VM, Baremetal, Load Balancer, floating IP, router) for up to **10** min per service instance. 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 Apr 27, 2026, 10:04 AM UTC

    We are happy to inform you that the partial outage in the Cloud 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 →