Skip to content

Outage tracker / Gcore / In the US

Is Gcore down in the US?

Vendor lists an old incident, not shown as liveWhat Gcore reports

Gcore still lists an incident opened on 2026-10-20, last updated 2026-11-03; it has been open past 72 hours, so we do not show it as live.

As of the last successful poll, 2026-11-05 17:59 UTC.

Gcore's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Gcore at Nov 5, 2026, 6:00 PM UTC.

Over the last 24 hours we completed 1038 checks from Ashburn and San Jose and 1038 answered cleanly, 100.00% availability.

Of the 2 other regions we check Gcore from, all 2 read checks passing right now.

Email me when Gcore reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Gcore's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing610 checks in 24h, 100.00%
San JoseChecks passing428 checks in 24h, 100.00%

Last checked Nov 5, 2026, 6:00 PM UTC.

Gcore from Ashburn and San Jose over the last 30 days

Over the last 30 days, Gcore answered our Ashburn probe in 630 ms on average, and 1 check in 20 took longer than 1,124 ms.

Over the last 30 days, Gcore answered our San Jose probe in 687 ms on average, and 1 check in 20 took longer than 1,117 ms.

Ranked by average response time across the 4 cities we check Gcore from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 273 ms and Tokyo slowest at 860 ms.

From Ashburn and San Jose we ran 3,230 checks of Gcore in 4 days, and 3,228 answered cleanly: 99.93% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.80% across 1,010 checks.

In Ashburn local time (EST), Gcore was slowest around 12 PM, at 773 ms on average over the last 14 days, and quickest around 9 AM, at 536 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5761100.00%633 ms
Wed, Nov 41,032100.00%627 ms
Tue, Nov 31,01099.80%638 ms
Mon, Nov 2427100.00%790 ms

Gcore outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Gcore outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Gcore from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 391 checks
TokyoChecks passing100.00% of 244 checks

Other countries we check Gcore from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Gcore's public endpoints. They are not user reports, and they are not Gcore's own status page.

See Gcore's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Gcore has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter