← HonkWatch.com

Is Quay down in Iran?

Planned maintenance at Quay

Iran 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, 16:58 UTC, 5 min ago · Official status page
Report a problem
Change country

Reports from people in Iran

Last 24 hours · Iran · times in UTC

0 reports

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

024 18:0000:0006:0012: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, 17:03 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 Iran

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

Our own checks of quay.io

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Dallas: loaded in 3213 ms Singapore: loaded in 2297 ms Lauterbourg: loaded in 519 ms Seattle: loaded in 584 ms São Paulo: loaded in 626 ms Doha: loaded in 850 ms Delhi: loaded in 1339 ms Portsmouth: loaded in 433 ms New Jersey: loaded in 757 ms Amsterdam: loaded in 508 ms Osaka: loaded in 831 ms Toronto: loaded in 118 ms Santiago: loaded in 748 ms Madrid: loaded in 540 ms St. Louis: loaded in 216 ms Los Angeles: loaded in 401 ms Seoul: loaded in 911 ms Bangalore: loaded in 1210 ms Mumbai: loaded in 1058 ms Querétaro: loaded in 309 ms Frankfurt: loaded in 543 ms Warsaw: loaded in 544 ms Sydney: loaded in 1517 ms Atlanta: loaded in 84 ms Tokyo: loaded in 809 ms Jakarta: loaded in 2150 ms New York: loaded in 51 ms Hong Kong: loaded in 994 ms Johannesburg: loaded in 1175 ms Hamina: loaded in 530 ms Tel Aviv: loaded in 679 ms London: loaded in 429 ms Melbourne: loaded in 1066 ms Port Louis: loaded in 1453 ms Cape Town: loaded in 1152 ms
  • DallasReachable3213 ms, 3 min ago
  • SingaporeReachable2297 ms, 3 min ago
  • LauterbourgReachable519 ms, 3 min ago
  • SeattleReachable584 ms, 3 min ago
  • São PauloReachable626 ms, 3 min ago
  • DohaReachable850 ms, 3 min ago
  • DelhiReachable1339 ms, 3 min ago
  • PortsmouthReachable433 ms, 3 min ago
  • New JerseyReachable757 ms, 3 min ago
  • AmsterdamReachable508 ms, 3 min ago
  • OsakaReachable831 ms, 3 min ago
  • TorontoReachable118 ms, 3 min ago
  • SantiagoReachable748 ms, 3 min ago
  • MadridReachable540 ms, 3 min ago
  • St. LouisReachable216 ms, 3 min ago
  • Los AngelesReachable401 ms, 4 min ago
  • SeoulReachable911 ms, 4 min ago
  • BangaloreReachable1210 ms, 4 min ago
  • MumbaiReachable1058 ms, 4 min ago
  • QuerétaroReachable309 ms, 4 min ago
  • FrankfurtReachable543 ms, 4 min ago
  • WarsawReachable544 ms, 4 min ago
  • SydneyReachable1517 ms, 4 min ago
  • AtlantaReachable84 ms, 4 min ago
  • TokyoReachable809 ms, 4 min ago
  • JakartaReachable2150 ms, 4 min ago
  • New YorkReachable51 ms, 4 min ago
  • Hong KongReachable994 ms, 4 min ago
  • JohannesburgReachable1175 ms, 4 min ago
  • HaminaReachable530 ms, 4 min ago
  • Tel AvivReachable679 ms, 4 min ago
  • LondonReachable429 ms, 5 min ago
  • MelbourneReachable1066 ms, 5 min ago
  • Port LouisReachable1453 ms, 5 min ago
  • Cape TownReachable1152 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

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

0%5%10% 18:0000:0006:0012:00 0% 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 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 12 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 Iran 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 Iran · Find another service