← HonkWatch.com

Is Quay down in Algeria?

Planned maintenance at Quay

Algeria No reports in the last hour checked 5 min ago
Quay has planned maintenance. Maintenance on Quay.io / API, Quay.io / Build System, Quay.io / Registry and 2 more. Updated 7 Nov, 18:17 UTC, 5 min ago · Official status page
Report a problem
Change country

Reports from people in Algeria

Last 24 hours · Algeria · times in UTC

0 reports

No community reports in the last 24 hours from Algeria. 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 7 Nov, 18:22 UTC

Report a problem with Quay

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Algeria

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

Our own checks of quay.io

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Seattle: loaded in 629 ms Dallas: loaded in 416 ms Singapore: loaded in 1246 ms São Paulo: loaded in 625 ms Doha: loaded in 847 ms Delhi: loaded in 1336 ms New Jersey: loaded in 371 ms Portsmouth: loaded in 415 ms Amsterdam: loaded in 475 ms Lauterbourg: loaded in 516 ms Osaka: loaded in 940 ms Toronto: loaded in 128 ms Madrid: loaded in 510 ms Santiago: loaded in 637 ms St. Louis: loaded in 214 ms Los Angeles: loaded in 410 ms Seoul: loaded in 1012 ms Frankfurt: loaded in 702 ms Querétaro: loaded in 302 ms Bangalore: loaded in 1217 ms Mumbai: loaded in 1024 ms Tokyo: loaded in 1179 ms Warsaw: loaded in 594 ms Atlanta: loaded in 146 ms New York: loaded in 48 ms Jakarta: loaded in 1144 ms Sydney: loaded in 1531 ms Hong Kong: loaded in 998 ms Tel Aviv: loaded in 672 ms Johannesburg: loaded in 1238 ms Hamina: loaded in 1151 ms London: loaded in 923 ms Melbourne: loaded in 1075 ms Cape Town: loaded in 1193 ms Port Louis: loaded in 1368 ms
  • SeattleReachable629 ms, 2 min ago
  • DallasReachable416 ms, 2 min ago
  • SingaporeReachable1246 ms, 2 min ago
  • São PauloReachable625 ms, 2 min ago
  • DohaReachable847 ms, 2 min ago
  • DelhiReachable1336 ms, 2 min ago
  • New JerseyReachable371 ms, 2 min ago
  • PortsmouthReachable415 ms, 2 min ago
  • AmsterdamReachable475 ms, 2 min ago
  • LauterbourgReachable516 ms, 2 min ago
  • OsakaReachable940 ms, 2 min ago
  • TorontoReachable128 ms, 2 min ago
  • MadridReachable510 ms, 2 min ago
  • SantiagoReachable637 ms, 2 min ago
  • St. LouisReachable214 ms, 2 min ago
  • Los AngelesReachable410 ms, 2 min ago
  • SeoulReachable1012 ms, 2 min ago
  • FrankfurtReachable702 ms, 3 min ago
  • QuerétaroReachable302 ms, 3 min ago
  • BangaloreReachable1217 ms, 3 min ago
  • MumbaiReachable1024 ms, 3 min ago
  • TokyoReachable1179 ms, 3 min ago
  • WarsawReachable594 ms, 3 min ago
  • AtlantaReachable146 ms, 3 min ago
  • New YorkReachable48 ms, 3 min ago
  • JakartaReachable1144 ms, 3 min ago
  • SydneyReachable1531 ms, 3 min ago
  • Hong KongReachable998 ms, 3 min ago
  • Tel AvivReachable672 ms, 3 min ago
  • JohannesburgReachable1238 ms, 3 min ago
  • HaminaReachable1151 ms, 3 min ago
  • LondonReachable923 ms, 3 min ago
  • MelbourneReachable1075 ms, 4 min ago
  • Cape TownReachable1193 ms, 4 min ago
  • Port LouisReachable1368 ms, 4 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

53.51% 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,920 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 00:0006:0012:0018:00 0% 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 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 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 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 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 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 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 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 103 checks failed0% of 107 checks failed0% of 107 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 failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed1% of 107 checks failed1% of 107 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 failed0% of 104 checks failed0% of 105 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 104 checks failed0% of 48 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 Algeria 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 Algeria · Find another service