Skip to content

Outage tracker / GitHub Container Registry / In Japan

Is GitHub Container Registry down in Japan?

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 17:00 UTC.

GitHub Container Registry'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 Japan, measured from Tokyo

Our Tokyo probe last checked GitHub Container Registry at Nov 6, 2026, 4:58 PM UTC and read checks passing.

Over the last 24 hours we completed 60 checks from Tokyo and 60 answered cleanly, 100.00% availability.

Of the 3 other regions we check GitHub Container Registry from, all 3 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.

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

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

What our Tokyo probe measured

TokyoChecks passing60 checks in 24h, 100.00%

Last checked Nov 6, 2026, 4:58 PM UTC.

GitHub Container Registry from Tokyo over the last 30 days

Over the last 30 days, GitHub Container Registry answered our Tokyo probe in 1,225 ms on average, and 1 check in 20 took longer than 2,031 ms.

Ranked by average response time across the 4 cities we check GitHub Container Registry from, Tokyo 4th; Frankfurt was fastest at 563 ms and Tokyo slowest at 1,225 ms.

From Tokyo we ran 256 checks of GitHub Container Registry in 5 days, and 256 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Tokyo local time (GMT+9), GitHub Container Registry was slowest around 8 PM, at 2,176 ms on average over the last 14 days, and quickest around 7 PM, at 757 ms.

Day (UTC)ChecksAvailabilityAverage response
Fri, Nov 641100.00%1,195 ms
Thu, Nov 562100.00%1,215 ms
Wed, Nov 463100.00%1,283 ms
Tue, Nov 361100.00%1,038 ms
Mon, Nov 229100.00%1,562 ms

GitHub Container Registry outages measured from Japan

Our Tokyo probe measured no confirmed GitHub Container Registry outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check GitHub Container Registry from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 143 checks
San JoseChecks passing100.00% of 112 checks
FrankfurtChecks passing100.00% of 100 checks

Other countries we check GitHub Container Registry from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe 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.

Japan 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 Tokyo

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