What is G-Core Labs's uptime?

Over the last 90 days, G-Core Labs reported 99.72% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.gcore.com, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see G-Core Labs's uptime history rolling forward in real time.

Has G-Core Labs had outages in 2026?

Yes, G-Core Labs has had 118 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last G-Core Labs outage?

The most recent G-Core Labs incident was "Hosting | Brazil, Fortaleza Incident Details", which started on October 30, 2026 and was resolved on October 30, 2026. Pingoru captured this directly from https://status.gcore.com. See the full incident card above for affected components and the update timeline.

How often does G-Core Labs have outages?

Based on the last 90 days, G-Core Labs averages 39.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is G-Core Labs's status page?

G-Core Labs's official status page is https://status.gcore.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is G-Core Labs down right now?

G-Core Labs is down. Pingoru checks the official status page every 5 minutes and flips this headline the moment G-Core Labs reports a change. Current status is based on 497 tracked services.

How does Pingoru know if G-Core Labs is down?

We read https://status.gcore.com directly, using G-Core Labs's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Where can I get notified when G-Core Labs has an outage?

Create a free Pingoru account and add G-Core Labs as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

G-Core Labs's status page says the service is up, but I'm having issues. What's wrong?

Three common reasons: • A real G-Core Labs incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real G-Core Labs issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official G-Core Labs status?

We use G-Core Labs's own status page at https://status.gcore.com and cross-reference their homepage (https://gcorelabs.com). Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Major Outage" mean?

G-Core Labs is reporting a major outage. A significant portion of the service is unavailable.

Is G-Core Labs down?

Last checked 4m ago

Current status

G-Core Labs is down

2 active incidents: [Scheduled] Cloud | Location Maintenance, Hosting | VMmanager and DCImanager control panels

Get alerts when G-Core Labs breaks → View G-Core Labs outage history →

Free, no credit card

Official status page: status.gcore.com
Checked every 5 minutes
497 components tracked

G-Core Labs is reporting a major outage right now (last checked 4m ago). 2 active incidents on the official status page.

Real-time G-Core Labs status, recent outages, and incident history: pulled directly from G-Core Labs's official status page at status.gcore.com every 5 minutes. Pingoru tracks 497 G-Core Labs services and has captured 120 incidents in the last 90 days (99.72% uptime). Get email, Slack, Discord, or webhook alerts the moment G-Core Labs reports a new incident, free for 3 monitors, no credit card.

Users who monitor G-Core Labs also follow these Cloud Infrastructure services:

Genesys Cloud View all 8,000+ providers

G-Core Labs uptime 99.72% uptime · past 90 days

Mon Wed Fri

AugSepOct

Less More

Active incident 1

Hosting | VMmanager and DCImanager control panels

Ongoing ● 13d 1h

Started Oct 18, 2026, 12:00 PM UTC

DCImanagerVMmanager
Timeline · 8 updates
- identified · Oct 18, 2026, 12:00 PM UTC
  
  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 currently not possible to create, stop, pause, or manage virtual or dedicated servers via the control panels. All existing servers continue to run normally. **What we have done:** The affected systems have been isolated and additional protective measures applied to prevent further unauthorized access. We are working with the vendor to verify whether any customer services or data were affected. We will provide an update as soon as we have more information. We apologize for the inconvenience.
- identified · Oct 20, 2026, 02:09 PM UTC
  
  $35
- identified · Oct 20, 2026, 02:10 PM UTC
  
  $43
- identified · Oct 23, 2026, 10:04 AM UTC
  
  We continue working on restoring our services and addressing the impact of the security incident. **At this stage, we have no evidence that customer data has ever been transferred outside Gcore's infrastructure. In parallel with recovery efforts, we are implementing additional security measures to prevent similar incidents in the future.** Services and dedicated server sales will be restored gradually across locations. We expect to reopen dedicated server sales in the first locations today, October 23, with additional locations becoming available progressively over the next week. We will continue to provide updates as recovery progresses. Thank you for your patience and understanding.
- monitoring · Oct 24, 2026, 07:24 PM UTC
  
  We implemented a fix and are currently monitoring the result.
- monitoring · Oct 24, 2026, 07:26 PM UTC
  
  We continue working on restoring full functionality of our management panels and addressing the impact of the security incident. At this stage, we still have no evidence that Gcore customer data has been transferred outside our infrastructure, which we consider an encouraging sign. Server management and new orders are now available again in the following locations: \- Singapore \- São Paulo \- Tel Aviv \- Ashburn Recovery efforts are ongoing for the remaining locations, which will become available gradually. If you have questions or urgent needs regarding specific locations, please contact our Support team. Your feedback will help us prioritize recovery efforts based on customer needs. We will continue sharing updates as we make progress. Thank you for your patience and understanding.
- identified · Oct 24, 2026, 11:07 PM UTC
  
  We continue working on restoring full functionality of our management panels and addressing the impact of the security incident. At this stage, we still have no evidence that Gcore customer data has been transferred outside our infrastructure, which we consider an encouraging sign. Server management and new orders are now available again in the following locations: VPS: São Paulo, Brazil USA, Ashburn DS: São Paulo, Brazil Israel, Tel Aviv Singapore South Africa, Johannesburg France, Paris Recovery efforts are ongoing for the remaining locations, which will become available gradually. If you have questions or urgent needs regarding specific locations, please contact our Support team. Your feedback will help us prioritize recovery efforts based on customer needs. We will continue sharing updates as we make progress. Thank you for your patience and understanding.
- identified · Oct 26, 2026, 09:58 AM UTC
  
  $47
Latest: $47

Recent outages & incidents

Past 90 days

Hosting | Brazil, Fortaleza Incident Details

Resolved 23m

Started Oct 30, 2026, 06:01 PM UTC · Resolved Oct 30, 2026, 06:24 PM UTC

Fortaleza (FLZ)
Timeline · 2 updates
- investigating · Oct 30, 2026, 06:01 PM UTC
  
  We are currently experiencing a partial outage in our Hosting services in the Fortaleza 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.
- resolved · Oct 30, 2026, 06:24 PM UTC
  
  We are happy to inform you that the partial outage in our hosting services for the **Fortaleza 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])
Latest: We are happy to inform you that the partial outage in our hosting services for the **Fortaleza region** has been resolved. However, if you continue to experience any issues, please…
Multiple Services | Astana Incident Details

Resolved 13h 6m

Started Oct 24, 2026, 07:28 PM UTC · Resolved Oct 25, 2026, 08:35 AM UTC

Astana (NLSA2)
Timeline · 3 updates
- investigating · Oct 24, 2026, 07:28 PM UTC
  
  We are currently experiencing a major outage in our NLSA2 Data Center, 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.
- identified · Oct 24, 2026, 10:43 PM UTC
  
  We are continuing to work on a fix for this incident.
- resolved · Oct 25, 2026, 08:35 AM UTC
  
  We are happy to inform you that the major outage in the NLSA2 Data Center 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])
Latest: We are happy to inform you that the major outage in the NLSA2 Data Center has been resolved. However, if you continue to experience any issues, please do not hesitate to contact ou…
CDN | Santiago de Queretaro Incident Details

Resolved 1h 51m

Started Oct 21, 2026, 06:14 AM UTC · Resolved Oct 21, 2026, 08:05 AM UTC

Santiago de Querétaro, Mexico
Timeline · 3 updates
- investigating · Oct 21, 2026, 06:14 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.
- identified · Oct 21, 2026, 06:17 AM UTC
  
  We are continuing to work on a fix for this incident.
- resolved · Oct 21, 2026, 08:05 AM UTC
  
  This incident has been resolved.
Latest: This incident has been resolved.
Hosting | Istanbul Incident Details

Resolved 5d 15h

Started Oct 17, 2026, 04:01 PM UTC · Resolved Oct 23, 2026, 07:44 AM UTC

Istanbul (TII)
Timeline · 2 updates
- investigating · Oct 17, 2026, 04:01 PM UTC
  
  We are currently experiencing a partial outage affecting our VPS hosting services in Istanbul, Turkey, 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 · Oct 23, 2026, 07:44 AM UTC
  
  We are happy to inform you that the partial outage in Istanbul has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support team. Our team will be happy to assist you and ensure that any further concerns are addressed promptly. We appreciate your patience and understanding throughout this incident, and we thank you for your cooperation. For further assistance, please contact our support team via [[email protected]](mailto:[email protected])
Latest: We are happy to inform you that the partial outage in Istanbul has been resolved. However, if you continue to experience any issues, please do not hesitate to contact our support t…
Cloud | Luxembourg-2 Incident Details

Resolved 41m

Started Oct 15, 2026, 12:43 PM UTC · Resolved Oct 15, 2026, 01:25 PM UTC

Block StorageContainersDatabaseFile Shares as a ServiceFunction as a ServiceManaged LoggingManaged PostgreSQLRegistryLuxembourg-2
Timeline · 3 updates
- investigating · Oct 15, 2026, 12:43 PM 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 provide updates as soon as more information becomes available on the progress of the resolution. Thank you for your understanding and cooperation.
- monitoring · Oct 15, 2026, 12:56 PM 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 soon as we have confirmed that the issue has been completely resolved.
- resolved · Oct 15, 2026, 01:25 PM 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 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]).
Latest: 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 re…

See the full G-Core Labs outage history

26 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse G-Core Labs outage history →

Or sign up free to get alerts when G-Core Labs breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Instatus · 497 components checked every 5 minutes

114incidents recorded

114last 12 months

31last 90 days

19 hourstypical duration, 12 months

The longest incident in the last year, Cloud | Amsterdam Incident Details on March 4, 2026, ran for 47 days. 224 maintenance windows announced in the same period.

Most affected components, last 12 months

Overall33
API6
Budapest (BIX)6
Statistics6
Content Delivery5

Latest incidents

Hosting | Brazil, Fortaleza Incident Details October 30, 2026 · 23 minutes · degraded service
We are currently experiencing a partial outage in our Hosting services in the Fortaleza region, which may result in partial unavailability for users. We…
Multiple Services | Astana Incident Details October 24, 2026 · 13 hours · major outage
We are currently experiencing a major outage in our NLSA2 Data Center, resulting in a complete unavailability of the service. We sincerely apologize for any…
CDN | Santiago de Queretaro Incident Details October 21, 2026 · 111 minutes · degraded service
We are currently experiencing a partial degradation in performance, and as a result, **we have rerouted traffic to nearby** locations to minimize the impact.…

Outage history

Past 90 days · 31 incidents View full outage history →

Hosting | Brazil, Fortaleza Incident Details Resolved

Started Oct 30, 2026, 06:01 PM UTC · Resolved Oct 30, 2026, 06:24 PM UTC · 23m
Multiple Services | Astana Incident Details Resolved

Started Oct 24, 2026, 07:28 PM UTC · Resolved Oct 25, 2026, 08:35 AM UTC · 13h 6m
CDN | Santiago de Queretaro Incident Details Resolved

Started Oct 21, 2026, 06:14 AM UTC · Resolved Oct 21, 2026, 08:05 AM UTC · 1h 51m
Hosting | VMmanager and DCImanager control panels Ongoing

Started Oct 18, 2026, 12:00 PM UTC · ● 13d 1h
Hosting | Istanbul Incident Details Resolved

Started Oct 17, 2026, 04:01 PM UTC · Resolved Oct 23, 2026, 07:44 AM UTC · 5d 15h
Cloud | Luxembourg-2 Incident Details Resolved

Started Oct 15, 2026, 12:43 PM UTC · Resolved Oct 15, 2026, 01:25 PM UTC · 41m
Cloud | Amsterdam Incident Details Resolved

Started Oct 11, 2026, 01:20 PM UTC · Resolved Oct 11, 2026, 04:23 PM UTC · 3h 3m
Customer Portal | Global Incident Details Resolved

Started Oct 07, 2026, 01:05 PM UTC · Resolved Oct 07, 2026, 01:44 PM UTC · 38m