We started checking Gcore on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Gcore reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Gcore's own status page declared. Below it, any public chatter we saw about Gcore and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Gcore's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Gcore in the last 24 hours, which is not evidence that nothing is wrong.
Gcore's status page
Hosting | VMmanager and DCImanager control panels: minor incidentStreaming | Live RTMP Ingestion Retrospective Incident Details: minor incident[Scheduled] Cloud & Hosting | Almaty (KAL) Maintenance: maintenance
Hosting | VMmanager and DCImanager control panels: minor incident, from before this window to now, still open per their page.
Streaming | Live RTMP Ingestion Retrospective Incident Details: minor incident, from before this window to now, still open per their page.
[Scheduled] Cloud & Hosting | Almaty (KAL) Maintenance: maintenance, from 01:00 UTC to 05:00 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Gcore's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Gcore next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
1930
US-West
99.85%
1300
Europe
100.00%
1206
Asia-Pacific
99.87%
753
Their declared record
Gcore's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Nov 20, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 10:58 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Warsaw (WA2) region. Due to the works, your Cloud services in Warsaw may experience up to 15 min of network unavailability/connectivity interrup…
Nov 19, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 10:25 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Amsterdam (DRA4) region. Due to the works, your Cloud / Hosting services in Amsterdam may experience up to 15 min of network unavailability/conn…
Nov 18, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 10:22 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Warsaw (PL1) region. Due to the works, your Hosting services in Warsaw may experience up to 15 min of network unavailability/connectivity interr…
Nov 17, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 10:11 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Frankfurt region. Due to the works, your Cloud services in Frankfurt-2 (FRN) / Hosting services in Frankfurt (FRN) may experience up to 15 min o…
[Scheduled] Cloud AI | Chester MaintenanceOngoing, maintenance
Nov 16, 2026, 9:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 13, 2026, 9:59 AM UTC): During this time period, our engineering team will be performing output breaker installation on Cloud AI, which may result in the service unavailability of up to 4 hours on each day. We are undertaking these measures to enhance the overall reliability and stability of the service…
[Scheduled] Hosting | New York (THNY) MaintenanceOngoing, maintenance
Nov 16, 2026, 7:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 10:05 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the New York (THNY) region. Due to the works, your Hosting services in New York may experience up to 15 min of network unavailability/connectivity i…
[Scheduled] Hosting | Milan (ML2) MaintenanceOngoing, maintenance
Nov 13, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 9:58 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Milan (ML2) region. Due to the works, your Hosting services in Milan may experience up to 15 min of network unavailability/connectivity interrup…
Nov 12, 2026, 8:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 9:54 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Manassas (ANX) region. Due to the works, your Cloud /Hosting services in Manassas may experience up to 15 min of network unavailability/connecti…
[Scheduled] Hosting | Seoul (KX) MaintenanceOngoing, maintenance
Nov 11, 2026, 5:00 PM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 9:47 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Seoul (KX) region. Due to the works, your Hosting services in Seoul may experience up to 15 min of network unavailability/connectivity interrupt…
Nov 10, 2026, 1:00 AM UTC, open for 0 min so faridentified
their latest update (Oct 12, 2026, 9:44 PM UTC): During this time period, our network engineering team will be performing a crucial software update of the network infrastructure in the Luxembourg-2 (ED-16) region. Due to the works, your Cloud services in Luxembourg-2 may experience up to 15 min of network unavailability/connect…
Showing the 10 most recent of 52 incidents Gcore has declared in the history we hold.
These entries are Gcore's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Gcore's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.