Is GitHub Container Registry down in the US?
Vendor reports no incidentWhat GitHub Container Registry reports
GitHub Container Registry reports no incident on its status page.
As of the last successful poll, 2026-11-06 16:27 UTC.
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 GitHub Container Registry at Nov 6, 2026, 4:22 PM UTC.
Over the last 24 hours we completed 256 checks from Ashburn and San Jose and 256 answered cleanly, 100.00% availability.
Of the 2 other regions we check GitHub Container Registry from, all 2 read checks passing right now.
Email me when GitHub Container Registry reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 6, 2026, 4:22 PM UTC.
GitHub Container Registry from Ashburn and San Jose over the last 30 days
Over the last 30 days, GitHub Container Registry answered our Ashburn probe in 650 ms on average, and 1 check in 20 took longer than 1,171 ms.
Over the last 30 days, GitHub Container Registry answered our San Jose probe in 908 ms on average, and 1 check in 20 took longer than 1,475 ms.
Ranked by average response time across the 4 cities we check GitHub Container Registry from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 563 ms and Tokyo slowest at 1,230 ms.
From Ashburn and San Jose we ran 1,045 checks of GitHub Container Registry in 5 days, and 1,045 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), GitHub Container Registry was slowest around 4 PM, at 921 ms on average over the last 14 days, and quickest around 1 PM, at 457 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Fri, Nov 6 | 171 | 100.00% | 818 ms |
| Thu, Nov 5 | 255 | 100.00% | 746 ms |
| Wed, Nov 4 | 260 | 100.00% | 621 ms |
| Tue, Nov 3 | 252 | 100.00% | 862 ms |
| Mon, Nov 2 | 107 | 100.00% | 833 ms |
GitHub Container Registry outages measured from the US
Our Ashburn and San Jose probes measured no confirmed GitHub Container Registry outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check GitHub Container Registry from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 101 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check GitHub Container Registry from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against GitHub Container Registry's public endpoints. They are not user reports, and they are not GitHub Container Registry's own status page.
See GitHub Container Registry'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 GitHub Container Registry 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 serversRun 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