by HonkWatch

Is Quay down in Lesotho?

Planned maintenance at Quay

Lesotho No reports in the last hour checked 3 min ago
Quay has planned maintenance. Maintenance on Quay.io / API, Quay.io / Build System, Quay.io / Registry and 2 more. Updated 6 Nov, 21:30 UTC, 3 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Lesotho

Last 24 hours · Lesotho · times in UTC

0 reports

No community reports in the last 24 hours from Lesotho. Having trouble? Add your report.

024 00:0006:0012:0018:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 21:33 UTC

Report a problem with Quay

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Lesotho

Monitor the provider status with HonkWatch

Get monitoring alerts for Quay

HonkWatch watches the Quay status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Quay is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Lesotho. The report chart above is filtered to Lesotho.

Our own checks of quay.io

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Portsmouth: loaded in 723 ms Seattle: loaded in 448 ms Lauterbourg: loaded in 485 ms New Jersey: loaded in 399 ms Cape Town: loaded in 1179 ms Doha: loaded in 951 ms Toronto: loaded in 118 ms Dallas: loaded in 202 ms St. Louis: loaded in 231 ms Delhi: loaded in 1747 ms Madrid: loaded in 468 ms London: loaded in 438 ms Santiago: loaded in 604 ms Hamina: loaded in 616 ms Singapore: loaded in 1298 ms Seoul: loaded in 916 ms Amsterdam: loaded in 2262 ms Osaka: loaded in 959 ms Mumbai: loaded in 1066 ms Johannesburg: loaded in 1137 ms Sydney: loaded in 1245 ms Hong Kong: loaded in 1007 ms Tokyo: loaded in 844 ms Frankfurt: loaded in 466 ms New York: loaded in 57 ms Querétaro: loaded in 312 ms Bangalore: loaded in 1593 ms Jakarta: loaded in 2226 ms Warsaw: loaded in 598 ms Port Louis: loaded in 1394 ms Atlanta: loaded in 117 ms Tel Aviv: loaded in 719 ms Melbourne: loaded in 1072 ms Los Angeles: loaded in 376 ms São Paulo: loaded in 626 ms
  • PortsmouthReachable723 ms, just now
  • SeattleReachable448 ms, just now
  • LauterbourgReachable485 ms, just now
  • New JerseyReachable399 ms, 1 min ago
  • Cape TownReachable1179 ms, 1 min ago
  • DohaReachable951 ms, 1 min ago
  • TorontoReachable118 ms, 1 min ago
  • DallasReachable202 ms, 1 min ago
  • St. LouisReachable231 ms, 1 min ago
  • DelhiReachable1747 ms, 2 min ago
  • MadridReachable468 ms, 2 min ago
  • LondonReachable438 ms, 2 min ago
  • SantiagoReachable604 ms, 2 min ago
  • HaminaReachable616 ms, 2 min ago
  • SingaporeReachable1298 ms, 2 min ago
  • SeoulReachable916 ms, 2 min ago
  • AmsterdamReachable2262 ms, 2 min ago
  • OsakaReachable959 ms, 2 min ago
  • MumbaiReachable1066 ms, 3 min ago
  • JohannesburgReachable1137 ms, 3 min ago
  • SydneyReachable1245 ms, 3 min ago
  • Hong KongReachable1007 ms, 4 min ago
  • TokyoReachable844 ms, 4 min ago
  • FrankfurtReachable466 ms, 4 min ago
  • New YorkReachable57 ms, 4 min ago
  • QuerétaroReachable312 ms, 4 min ago
  • BangaloreReachable1593 ms, 4 min ago
  • JakartaReachable2226 ms, 4 min ago
  • WarsawReachable598 ms, 4 min ago
  • Port LouisReachable1394 ms, 4 min ago
  • AtlantaReachable117 ms, 4 min ago
  • Tel AvivReachable719 ms, 4 min ago
  • MelbourneReachable1072 ms, 4 min ago
  • Los AngelesReachable376 ms, 8 min ago
  • São PauloReachable626 ms, 8 min ago

This is separate from the status page: we request quay.io and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Quay

Red Hat

Quay.io

  • APIMaintenance
  • Build SystemMaintenance
  • RegistryMaintenance
  • FrontendMaintenance
  • Security ScanningMaintenance

114 other parts are working.

Incidents and maintenance

Maintenance

  • Ask Red Hat DB minor version patching (planned) 14 Nov, 05:00 UTC to 14 Nov, 06:00 UTC. Affects Ask · Details
  • Quay.io Read-Only Mode (planned) 21 Nov, 10:00 UTC to 21 Nov, 12:00 UTC. Affects API, Build System, Registry, Frontend and 1 more · Details
Outage history

Last problem: 6 Nov, 11:53 UTC, partial outage for 19 min (1 of 119 parts affected: docs.redhat.com / Product Hub).

Last 9030 days

44.40% of the time without a reported outage, since 2 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of quay.io that failed (9,506 checks). Shaded: when Quay's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%10%20% 00:0006:0012:0018:00 0% of 102 checks failed0% of 108 checks failed0% of 105 checks failed0% of 108 checks failed0% of 103 checks failed0% of 101 checks failed0% of 105 checks failed0% of 108 checks failed0% of 106 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 106 checks failed4% of 117 checks failed20% of 131 checks failed16% of 129 checks failed12% of 120 checks failed0% of 106 checks failed0% of 105 checks failed0% of 104 checks failed0% of 105 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed2% of 111 checks failed0% of 105 checks failed0% of 105 checks failed0% of 102 checks failed0% of 108 checks failed1% of 105 checks failed0% of 103 checks failed0% of 109 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 101 checks failed0% of 102 checks failed0% of 94 checks failed0% of 100 checks failed0% of 100 checks failed0% of 103 checks failed0% of 102 checks failed0% of 81 checks failed0% of 75 checks failed0% of 105 checks failed0% of 89 checks failed0% of 105 checks failed0% of 98 checks failed0% of 100 checks failed0% of 71 checks failed0% of 101 checks failed0% of 96 checks failed0% of 97 checks failed0% of 85 checks failed0% of 93 checks failed0% of 93 checks failed0% of 86 checks failed0% of 100 checks failed0% of 86 checks failed0% of 69 checks failed0% of 91 checks failed0% of 77 checks failed0% of 86 checks failed0% of 82 checks failed0% of 90 checks failed0% of 99 checks failed0% of 90 checks failed0% of 93 checks failed0% of 103 checks failed0% of 91 checks failed0% of 98 checks failed0% of 81 checks failed0% of 109 checks failed0% of 82 checks failed0% of 85 checks failed0% of 91 checks failed0% of 104 checks failed0% of 80 checks failed0% of 95 checks failed0% of 110 checks failed0% of 104 checks failed0% of 106 checks failed0% of 87 checks failed0% of 100 checks failed0% of 22 checks failed

Recent problems

6 Nov, 11:53 UTCPartial outage19 min1 of 119 parts affected: docs.redhat.com / Product Hub
6 Nov, 11:11 UTCPartial outage4 min1 of 119 parts affected: docs.redhat.com / Content
6 Nov, 10:12 UTCPartial outage32 min1 of 119 parts affected: docs.redhat.com / Product Hub
5 Nov, 11:24 UTCPartial outage7 h 19 minOpen incident: Docs.redhat.com - Intermittent performance degradation
5 Nov, 10:05 UTCPartial outage24 min2 of 119 parts affected: docs.redhat.com / Homepage, docs.redhat.com / Product Hub
5 Nov, 09:43 UTCPartial outage14 min1 of 119 parts affected: docs.redhat.com / Product Hub
5 Nov, 08:09 UTCPartial outage1 h 26 min2 of 119 parts affected: docs.redhat.com / Homepage, docs.redhat.com / Product Hub
5 Nov, 07:37 UTCPartial outage8 min1 of 119 parts affected: docs.redhat.com / Content
5 Nov, 07:14 UTCPartial outage8 min1 of 119 parts affected: docs.redhat.com / Product Hub
5 Nov, 05:42 UTCPartial outage16 min2 of 119 parts affected: docs.redhat.com / Content, docs.redhat.com / Product Hub
What can I try?

Having trouble with Quay?

  1. Compare reports from Lesotho and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Quay down, or is it just me?

Quay is doing planned maintenance, so some parts may not work right now. It is probably not just you.

How do we know?

We read the official Quay status page and load quay.io from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Developer tools

See the live outage feed for Lesotho · Find another service