Gcore

Affected: Santiago de Querétaro, Mexico

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 06:14 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...

2. identified 2026-10-21 06:17 UTC

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

3. resolved 2026-10-21 08:05 UTC

   We are happy to inform you that traffic has been successfully rerouted back to Santiago de Queretaro 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: DCImanager, VMmanager

1. identified 2026-10-18 12:00 UTC

   **All existing servers continue to run normally.** The VMmanager and DCImanager control panels in Hosting in all locations have been temporarily disabled following the discovery of a security vulnerability in third-party software provided by our vendor. **Impact:** It is...

2. identified 2026-10-20 14:09 UTC

   This incident affects Gcore Hosting only (VPS managed through the VMmanager). **We have no indication that other Gcore products, including Cloud and CDN, are affected.** The control panels were disabled after attackers exploited a vulnerability in third-party virtualization...

3. identified 2026-10-20 14:10 UTC

   This incident affects Gcore Hosting only (VPS managed through the VMmanager). **We have no indication that other Gcore products, including Cloud and CDN, are affected.** The control panels were disabled after attackers exploited a vulnerability in third-party virtualization...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Istanbul (TII)

1. identified 2026-10-17 16:01 UTC

   We have identified the root cause of the incident and are actively working on implementing a resolution. We will continue to provide updates as progress is made.

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Luxembourg-2, File Shares as a Service, Managed Logging, Block Storage, Managed PostgreSQL, Registry, Containers, Function as a Service, Database

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 12:43 UTC

   We are currently experiencing a partial outage of all Platform Services in ED-16 (Luxembourg-2), 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...

2. monitoring 2026-10-15 12:56 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the partial outage of all Platform Services in ED-16 (Luxembourg-2). However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as...

3. resolved 2026-10-15 13:25 UTC

   We are happy to inform you that the partial outage affecting Platform Services in ED-16 (Luxembourg-2), which resulted in partial service unavailability for some users, has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Amsterdam

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-11 13:20 UTC

   We are currently experiencing a partial outage in our Cloud - networking services - Amsterdam region, which may result in partial unavailability, redundancy loss for some users. We apologize for any inconvenience this may cause and appreciate your patience and understanding...

2. monitoring 2026-10-11 14:08 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve partial outage in Cloud- networking services. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have...

3. resolved 2026-10-11 16:23 UTC

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

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Customer Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 13:05 UTC

   We are currently experiencing a major outage in our Customer Portal, resulting in a complete unavailability of the service and problems with login. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding during this...

2. identified 2026-10-07 13:25 UTC

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

3. resolved 2026-10-07 13:44 UTC

   We are happy to inform you that the major outage in our 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Johannesburg

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-06 01:30 UTC

   We would like to inform you that between 1:30 UTC 06/10/2026 and 2:00 UTC 06/10/2026, our engineers observed a degradation in Cloud backend connectivity in Johannesburg. However, our team took swift action to resolve the issue, and we are pleased to confirm that the connectivity...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Amsterdam

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-04 10:56 UTC

   We are currently experiencing performance degradation in our Cloud bare-metal services , 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...

2. identified 2026-10-04 13:08 UTC

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

3. monitoring 2026-10-04 16:00 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the performance degradation in our Cloud bare-metal services. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon...

4. resolved 2026-10-04 16:24 UTC

   We are happy to inform you that the performance degradation affecting Cloud bare-metal 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Kyiv (GN)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-03 09:48 UTC

   We are currently experiencing a partial outage of our Hosting services in Kyiv 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...

2. monitoring 2026-10-03 14:12 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolvea partial outage of our Hosting services in Kyiv location. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we...

3. resolved 2026-10-03 17:42 UTC

   We are happy to inform you that the partial outage of our Hosting services in Kyiv location 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Amsterdam

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-03 02:08 UTC

   We are currently experiencing performance degradation in our Cloud bare-metal services , 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...

2. monitoring 2026-10-03 03:04 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the performance degradation in our Cloud bare-metal services. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon...

3. resolved 2026-10-03 10:16 UTC

   We are happy to inform you that the performance degradation affecting Cloud bare-metal 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Madrid (CM)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 14:00 UTC

   We are currently experiencing a major outage of our Hosting services in Madrid 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...

2. identified 2026-10-02 16:12 UTC

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

3. monitoring 2026-10-02 17:03 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve major outage of our Hosting services in Madrid region. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we...

4. resolved 2026-10-02 20:09 UTC

   We are happy to inform you that the major outage of our Hosting services in Madrid 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Customer Portal, Almaty

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-30 11:50 UTC

   We are currently experiencing a partial outage affecting Cloud operations in Almaty. Some actions in the Customer Portal may be temporarily unavailable, while existing instances remain up and running. We apologize for any inconvenience this may cause and appreciate your patience...

2. resolved 2026-09-30 13:28 UTC

   We are happy to inform you that the partial outage affecting Cloud operations in Almaty, which caused some Customer Portal actions to be temporarily unavailable, has been resolved. All services are now operating normally. However, if you continue to experience any issues, please...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Kharkiv, Ukraine, Kyiv, Ukraine, Kyiv (GN)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 08:39 UTC

   We are currently experiencing a major outage in our CDN in Kiev and Kharkiv - We have rerouted traffic to nearby locations to minimize the impact. Our Hosting services in Kyiv are also affected resulting in a complete unavailability of the service. We sincerely apologize for any...

2. identified 2026-09-23 13:39 UTC

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

3. monitoring 2026-09-24 19:03 UTC

   We are pleased to inform you that our engineering team has successfully rerouted the traffic back to **Kharkiv**. 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...

4. resolved 2026-09-25 09:21 UTC

   We are happy to inform you that the major outage affecting our CDN services in Kyiv and Kharkiv, as well as our Hosting services in Kyiv, has been resolved. Traffic has been fully restored to the affected locations, and all services are operating normally. However, if you...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Warsaw, Poland, Warsaw, Warsaw (PL1)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-22 11:35 UTC

   We are currently experiencing a partial outage with our connectivity in the WA2 and PL1 datacenter, 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. Services...

2. monitoring 2026-09-22 11:50 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the partial connectivity outage affecting the WA2 and PL1 data centers, which was causing partial service unavailability for some users. At this time, affected services, including Cloud,...

3. monitoring 2026-09-22 12:37 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve our connectivity in the WA2 and PL1 datacenter. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update as soon as we have...

4. resolved 2026-09-22 13:51 UTC

   We are happy to inform you that the degradation in connectivity with our PL1 and WA2 data centers 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Fortaleza (FLZ), Atlanta (ATL2), Lima (LLP), Los Angeles (LA2)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 05:59 UTC

   We are currently experiencing a partial outage in our Hosting services in Fortaleza (FLZ), Lima (LLP), Atlanta (ATL2), and Los Angeles (LA2), which may result in partial unavailability for users. We apologize for any inconvenience this may cause and appreciate your patience and...

2. resolved 2026-09-18 09:30 UTC

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

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Baku (DTA), Buenos Aires, Chișinău (MLT)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 03:08 UTC

   We are currently experiencing a partial outage in our Hostig services in Baku (DTA), Chisinau (MLT) and Buenos Aires. (EZEN) which may result in partial unavailability for users. We apologize for any inconvenience this may cause and appreciate your patience and understanding...

2. resolved 2026-09-17 06:01 UTC

   We are happy to inform you that the partial outage of Hosting services in Baku (DTA), Chisinau (MLT) and Buenos Aires (EZEN) 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...

3. investigating 2026-09-17 07:42 UTC

   This is to inform you that the issue with MLT region (Chișinău) has reoccurred after a previous fix was applied. We are resuming our investigation to identify and resolve the root cause as quickly as possible. Customers may continue to experience partial unavailability during...

4. resolved 2026-09-17 08:17 UTC

   We are happy to inform you that the partial outage of hosting services in all locations - Chișinău (MLT) Baku (DTA), and Buenos Aires (EZEN) has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Budapest (BIX), Bucharest (BU2), Sofia (TSC)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-15 23:56 UTC

   We are currently experiencing a partial outage in our Hosting Services in Budapest, Sofia, Bucharest, 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...

2. resolved 2026-09-16 02:42 UTC

   We are happy to inform you that the partial outage in our Hosting Services in Budapest, Sofia, Bucharest 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Luxembourg

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-15 19:30 UTC

   We are currently experiencing a major outage in our Cloud VMs drives being in read-only or unavailalbe state, resulting in a complete unavailability of the service. We sincerely apologize for any inconvenience this may cause and greatly appreciate your patience and understanding...

2. monitoring 2026-09-15 20:12 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the issue affecting Cloud VM drives that were entering a read-only or unavailable state, resulting in service unavailability. However, we are still closely monitoring the situation to ensure...

3. monitoring 2026-09-15 20:35 UTC

   We implemented a fix and are currently monitoring the result.

4. resolved 2026-09-15 20:56 UTC

   We are happy to inform you that the Major Cloud VM issue 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Luxembourg

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-13 04:53 UTC

   We are currently experiencing performance degradation in our Cloud Virtual Machine and Load balancer creation in Luxembourg ED-16, which may result in slow or unusual functioning of our services. We sincerely apologize for any inconvenience this may cause and greatly appreciate...

2. monitoring 2026-09-13 05:21 UTC

   We are pleased to inform you that our engineering team has implemented a fix to address the performance degradation affecting Cloud Virtual Machine and Load Balancer creation in Luxembourg ED-16. We are continuing to closely monitor the situation to ensure that service...

3. resolved 2026-09-13 07:12 UTC

   We are happy to inform you that the performance degradation affecting Cloud Virtual Machine and Load Balancer creation in Luxembourg ED-16 has been resolved. If you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Santiago de Querétaro (SQR)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 12:04 UTC

   We are currently experiencing a major outage in our Hosting service in Santiago de Queretaro, 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...

2. identified 2026-09-11 12:11 UTC

   We are currently experiencing an outage in our Hosting service in Santiago de Queretaro, which may result in unavailability for users up to 15 minutes. It is caused by urgent network equipment update. We apologize for any inconvenience this may cause and appreciate your patience...

3. resolved 2026-09-11 13:05 UTC

   We are happy to inform you that the a major outage in our Hosting service in Santiago de Queretaro 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Statistics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-08 15:01 UTC

   We are currently experiencing a partial outage in our CDN Statistics, which may result in a delay in observed statistics, we are not expecting any data loss. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We...

2. identified 2026-09-08 15:15 UTC

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

3. monitoring 2026-09-08 19:41 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve delays in reported CDN Statistics data in the CDN Statistics service. However, we are still closely monitoring the situation to ensure stable performance. We will provide you with an update...

4. resolved 2026-09-08 20:20 UTC

   We are happy to inform you that the delay in the reported CDN Statistics data in the CDN Statistics 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Porto Alegre, Brazil

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-05 22:03 UTC

   We are currently experiencing a major 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...

2. monitoring 2026-09-05 22:24 UTC

   We are pleased to inform you that our engineering team has successfully rerouted the traffic back to Panama. 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...

3. resolved 2026-09-05 22:52 UTC

   We are happy to inform you that traffic has been successfully rerouted back to Panama 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Customer Portal

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 11:41 UTC

   We are currently experiencing a partial outage affecting the Control Plane for Virtual Instances in ANX-2, Manassas. Customers may be unable to perform management actions (create, start, stop, resize, etc.) on Virtual Instances. All existing Virtual Instances remain up and...

2. identified 2026-08-27 11:44 UTC

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

3. monitoring 2026-08-27 11:45 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve a partial outage affecting the Control Plane for Virtual Instances in ANX-2, Manassas. However, we are still closely monitoring the situation to ensure stable performance. We will provide you...

4. resolved 2026-08-27 12:14 UTC

   We are happy to inform you that the partial outage affecting the Control Plane for Virtual Instances in ANX-2, Manassas 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: Customer Portal

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 09:50 UTC

   We are currently experiencing a partial outage affecting the Control Plane for Virtual Instances in ED-16, Luxembourg-2\. Customers may be unable to perform management actions (create, start, stop, resize, etc.) on Virtual Instances. All existing Virtual Instances remain up and...

2. identified 2026-08-26 09:52 UTC

   We've identified the cause of the issue affecting the Control Plane. Existing instances continue to run normally; management operations (create/start/stop/resize) may be impacted. Our team is implementing a fix. Updates to follow.

3. monitoring 2026-08-26 11:50 UTC

   We are pleased to inform you that our engineering team has implemented a fix to resolve the issue. 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...

4. resolved 2026-08-26 12:06 UTC

   We are happy to inform you that the issue 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...

Excerpts are shortened. Read the full incident on Gcore's status page.

Affected: San Jose, United States, Nebraska, United States, Managua, Nicaragua, Caracas, Venezeula, Boston, United States, Denver, United States, Alto Parana, Paraguay, Asunción, Paraguay, Guatemala City, Guatemala, Guayaquil, Ecuador, Quito, Ecuador, São Paulo, Brazil, Tegucigalpa, Honduras, Los Angeles, United States, Manassas, United States, Chicago (DRC), United States, Minneapolis, United States, Toronto, Canada, Bogota, Colombia, Lima, Peru, McAllen, United States, Ashburn, United States, Rio de Janeiro, Brazil, Santa Cruz de la sierra, Bolivia, Chicago (CCH1), United States, El Paso, United States, Santiago de Querétaro, Mexico, Atlanta, United States, Dallas, United States, Miami, United States, New York, United States, Seattle, United States, Buenos Aires, Argentina, Fortaleza, Brazil, Maracaibo, Venezuela, Panama City, Panama, Porto Alegre, Brazil, San José, Costa Rica, San Salvador, El Salvador, Santiago de Chile, Chile

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-23 02:32 UTC

   We are currently experiencing a partial outage in our CDN, 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...

2. identified 2026-08-23 03:04 UTC

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

3. monitoring 2026-08-23 03:27 UTC

   We implemented a fix and are currently monitoring the result.

4. resolved 2026-08-23 03:27 UTC

   We are happy to inform you that the partial outage in our CDN 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...

Excerpts are shortened. Read the full incident on Gcore's status page.