- 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
-
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])
-
resolved Apr 30, 2026, 04:21 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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])
-
resolved Apr 29, 2026, 10:00 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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 →
- Detected by Pingoru
- Apr 24, 2026, 12:06 PM UTC
- Resolved
- Apr 24, 2026, 01:08 PM UTC
- Duration
- 1h 1m
Affected: GcoreDDoS Protection (Statistics)
Timeline · 2 updates
-
investigating Apr 24, 2026, 12:06 PM UTC
We are currently experiencing a partial outage in our DDoS Protection service affecting 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.
-
resolved Apr 24, 2026, 01:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 11:35 AM UTC
- Resolved
- Apr 25, 2026, 12:10 AM UTC
- Duration
- 12h 34m
Affected: GcoreCloud (Database)Compute (Luxembourg-2)
Timeline · 4 updates
-
investigating Apr 24, 2026, 11:35 AM UTC
We are currently experiencing a partial outage in our Cloud services in 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 provide updates as soon as more information becomes available on the progress of the resolution. Thank you for your understanding and cooperation. For further information or assistance, please do not hesitate to contact our support team via [**[email protected]**](mailto:[email protected])
-
identified Apr 24, 2026, 02:34 PM UTC
We are currently experiencing a partial outage in our Cloud services in Luxembourg-2, which may result in partial unavailability for users. The issue has been identified by our team. 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. For further information or assistance, please do not hesitate to contact our support team via [**[email protected]**](mailto:[email protected])
-
monitoring Apr 24, 2026, 04:27 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Apr 25, 2026, 12:10 AM UTC
We are happy to inform you that the partial outage in our Cloud services in 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. 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 →
- Detected by Pingoru
- Apr 23, 2026, 03:35 PM UTC
- Resolved
- Apr 23, 2026, 07:03 PM UTC
- Duration
- 3h 28m
Affected: Gcore
Timeline · 2 updates
-
investigating Apr 23, 2026, 03:35 PM UTC
Our engineering team is currently conducting power maintenance in our Luxembourg data center. This is expected to last up to 2,5hrs. During this time no service interruption is expected. We apologize for any inconvenience this may cause and appreciate your patience and understanding. 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])
-
resolved Apr 23, 2026, 07:03 PM UTC
We are happy to inform you that the Power Maintenance 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 →
- Detected by Pingoru
- Apr 23, 2026, 02:53 AM UTC
- Resolved
- Apr 23, 2026, 05:21 AM UTC
- Duration
- 2h 27m
Affected: GcoreEurope (Budapest, Hungary)Europe (Budapest (BIX))
Timeline · 3 updates
-
investigating Apr 23, 2026, 02:53 AM UTC
We are currently experiencing a major outage in our CDN and Hosting services in Budapest region due to planned works in transit ISP, 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.
-
monitoring Apr 23, 2026, 03:23 AM UTC
We are pleased to inform you that our engineering team has implemented a fix to resolve major outage in CDN and Hosting 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 confirmed that the issue has been completely resolved.
-
resolved Apr 23, 2026, 05:21 AM UTC
We are happy to inform you that the major outage in our CDN and Hosting 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 →
- Detected by Pingoru
- Apr 21, 2026, 09:52 AM UTC
- Resolved
- Apr 21, 2026, 11:11 AM UTC
- Duration
- 1h 19m
Affected: GcoreStreaming (API)
Timeline · 3 updates
-
investigating Apr 21, 2026, 09:52 AM UTC
We are currently experiencing a partial outage in our Streaming API service, 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.
-
monitoring Apr 21, 2026, 10:49 AM UTC
We are pleased to inform you that our engineering team has implemented a fix to resolve the partial outage in our Streaming API service. 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.
-
resolved Apr 21, 2026, 11:11 AM UTC
We are happy to inform you that the partial outage in our Streaming API 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 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])
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 08:34 AM UTC
- Resolved
- Apr 20, 2026, 08:34 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 09:20 PM UTC
- Resolved
- Apr 19, 2026, 09:20 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 03:59 AM UTC
- Resolved
- Apr 19, 2026, 03:59 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 11:46 PM UTC
- Resolved
- Apr 16, 2026, 11:46 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 11:42 AM UTC
- Resolved
- Apr 13, 2026, 11:42 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 01:39 AM UTC
- Resolved
- Apr 13, 2026, 01:39 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 05:24 AM UTC
- Resolved
- Apr 12, 2026, 05:24 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 12:49 PM UTC
- Resolved
- Apr 10, 2026, 12:49 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 11:33 AM UTC
- Resolved
- Apr 07, 2026, 11:33 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 10:28 AM UTC
- Resolved
- Apr 07, 2026, 10:28 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 10:04 AM UTC
- Resolved
- Apr 07, 2026, 10:04 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 07:27 AM UTC
- Resolved
- Apr 06, 2026, 07:27 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 10:04 PM UTC
- Resolved
- Apr 02, 2026, 10:04 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 03:06 PM UTC
- Resolved
- Apr 02, 2026, 03:06 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 02:42 PM UTC
- Resolved
- Mar 31, 2026, 02:42 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 04:17 PM UTC
- Resolved
- Mar 30, 2026, 04:17 PM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 11:00 AM UTC
- Resolved
- Mar 25, 2026, 11:00 AM UTC
- Duration
- —
Affected: Gcore
Read the full incident report →