by HonkWatch

Is Quay down in Brunei?

Planned maintenance at Quay

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

Reports from people in Brunei

Last 24 hours · Brunei · times in UTC

0 reports

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

024 06:0012:0018:0000: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 7 Nov, 00:53 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 Brunei

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 Brunei. The report chart above is filtered to Brunei.

Our own checks of quay.io

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Johannesburg: loaded in 1105 ms Tel Aviv: loaded in 680 ms Hamina: loaded in 541 ms Lauterbourg: loaded in 538 ms London: loaded in 395 ms Melbourne: loaded in 1069 ms Port Louis: loaded in 1407 ms Cape Town: loaded in 1130 ms Dallas: loaded in 412 ms Seattle: loaded in 328 ms Singapore: loaded in 1116 ms São Paulo: loaded in 626 ms Portsmouth: loaded in 631 ms Delhi: loaded in 1320 ms Doha: loaded in 885 ms New Jersey: loaded in 1484 ms Amsterdam: loaded in 495 ms Osaka: loaded in 980 ms Toronto: loaded in 132 ms Madrid: loaded in 536 ms Santiago: loaded in 752 ms St. Louis: loaded in 192 ms Los Angeles: loaded in 369 ms Seoul: loaded in 918 ms Frankfurt: loaded in 445 ms Querétaro: loaded in 292 ms Bangalore: loaded in 1218 ms Mumbai: loaded in 1015 ms Atlanta: loaded in 88 ms Warsaw: loaded in 593 ms Tokyo: loaded in 778 ms Sydney: loaded in 1488 ms New York: loaded in 254 ms Jakarta: loaded in 1146 ms Hong Kong: loaded in 995 ms
  • JohannesburgReachable1105 ms, just now
  • Tel AvivReachable680 ms, just now
  • HaminaReachable541 ms, just now
  • LauterbourgReachable538 ms, just now
  • LondonReachable395 ms, just now
  • MelbourneReachable1069 ms, just now
  • Port LouisReachable1407 ms, just now
  • Cape TownReachable1130 ms, just now
  • DallasReachable412 ms, 3 min ago
  • SeattleReachable328 ms, 3 min ago
  • SingaporeReachable1116 ms, 4 min ago
  • São PauloReachable626 ms, 4 min ago
  • PortsmouthReachable631 ms, 4 min ago
  • DelhiReachable1320 ms, 4 min ago
  • DohaReachable885 ms, 4 min ago
  • New JerseyReachable1484 ms, 4 min ago
  • AmsterdamReachable495 ms, 4 min ago
  • OsakaReachable980 ms, 4 min ago
  • TorontoReachable132 ms, 4 min ago
  • MadridReachable536 ms, 4 min ago
  • SantiagoReachable752 ms, 4 min ago
  • St. LouisReachable192 ms, 4 min ago
  • Los AngelesReachable369 ms, 4 min ago
  • SeoulReachable918 ms, 4 min ago
  • FrankfurtReachable445 ms, 4 min ago
  • QuerétaroReachable292 ms, 4 min ago
  • BangaloreReachable1218 ms, 4 min ago
  • MumbaiReachable1015 ms, 5 min ago
  • AtlantaReachable88 ms, 5 min ago
  • WarsawReachable593 ms, 5 min ago
  • TokyoReachable778 ms, 5 min ago
  • SydneyReachable1488 ms, 5 min ago
  • New YorkReachable254 ms, 5 min ago
  • JakartaReachable1146 ms, 5 min ago
  • Hong KongReachable995 ms, 5 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

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

Of the last 90 days, 5 had a partial or major outage, 1 had maintenance only and 84 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,529 checks). Shaded: when Quay's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%10%20% 06:0012:0018:0000:00 0% 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 114 checks failed0% of 94 checks failed0% of 107 checks failed0% of 96 checks failed0% of 113 checks failed0% of 105 checks failed0% of 101 checks failed0% of 109 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 47 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 Brunei 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 Brunei · Find another service