Skip to content

Outage tracker / Quay.io / In Japan

Is Quay.io down in Japan?

Vendor reports an incidentWhat Quay.io reports

Quay.io reports an incident on its status page: Docs.redhat.com - Intermittent performance degradation.

Impact: major. Since 2026-11-05 11:40 UTC.

Latest update, 2026-11-05 11:40 UTC: We are experiencing intermittent performance issues on docs.redhat.com. Some users may see slow page loads, timeouts, or pages that fail to load. We are currently investigating the issue.

Quay.io'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 Quay.io at Nov 5, 2026, 2:48 PM UTC and read checks passing.

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

Of the 3 other regions we check Quay.io from, all 3 read checks passing right now.

Email me when Quay.io 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 Quay.io's own statement from its status page, with our regional reading beside it.

What our Tokyo probe measured

TokyoChecks passing61 checks in 24h, 100.00%

Last checked Nov 5, 2026, 2:48 PM UTC.

Quay.io from Tokyo over the last 30 days

Over the last 30 days, Quay.io answered our Tokyo probe in 2,429 ms on average, and 1 check in 20 took longer than 3,056 ms.

Ranked by average response time across the 4 cities we check Quay.io from, Tokyo 4th; Ashburn was fastest at 811 ms and Tokyo slowest at 2,429 ms.

From Tokyo we ran 185 checks of Quay.io in 4 days, and 184 answered cleanly: 99.45% availability.

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

In Tokyo local time (GMT+9), Quay.io was slowest around 9 AM, at 3,338 ms on average over the last 14 days, and quickest around 6 AM, at 2,053 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 540100.00%2,147 ms
Wed, Nov 458100.00%2,503 ms
Tue, Nov 36098.33%2,393 ms
Mon, Nov 227100.00%2,772 ms

Quay.io outages measured from Japan

Our Tokyo probe measured no confirmed Quay.io outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check Quay.io from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 145 checks
San JoseChecks passing100.00% of 114 checks
FrankfurtChecks passing100.00% of 101 checks

Other countries we check Quay.io from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe against Quay.io's public endpoints. They are not user reports, and they are not Quay.io's own status page.

See Quay.io'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 Quay.io 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