← HonkWatch.com

Is Red Hat down in Fr. S. Antarctic Lands?

Planned maintenance at Red Hat

People in Fr. S. Antarctic Lands: 0 reports in the last hour Official page: Planned maintenance, checked 2 min ago Our checks: loads from 35 of 35 places

API: Maintenance

Red Hat has planned maintenance. Maintenance on Quay.io / API, Quay.io / Build System, Quay.io / Registry and 2 more. Updated 7 Nov, 20:39 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Red Hat's status page)

Maintenance

  • Ask Red Hat DB minor version patching (planned) 14 Nov, 05:00 UTC to 14 Nov, 06:00 UTC. Affects Ask · Details Latest update (6 Nov, 09:55 UTC): Aurora PostgreSQL Database minor version patching schedule
  • 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 Latest update (6 Nov, 18:56 UTC): Quay.io will be in read-only mode on Saturday, November 21, 2026, from 10:00 AM to 12:00 PM EST (15:00–17:00 UTC) for planned database maintenance. During this window: - Image pulls will continue to work normally. - Pushes will fail with a read-only error. - Write operations in the UI and API will b

In Red Hat's own words, as we read them every 2.5 minutes, last 2 min ago. Read Red Hat's status page

Reports from people in Fr. S. Antarctic Lands

Last 24 hours · Fr. S. Antarctic Lands · times in UTC

0 reports

No community reports in the last 24 hours from Fr. S. Antarctic Lands. Having trouble? Add your report.

Status page: maintenance, 6 Nov, 18:57 to now 024 00:0006:0012:0018:00 20:45-21:00 UTC: 35 of 35 places loaded it, typical 546 to 749 ms21:00-21:05 UTC: 20 of 20 places loaded it, typical 704 ms21:05-21:10 UTC: 26 of 26 places loaded it, typical 908 ms21:10-21:25 UTC: 35 of 35 places loaded it, typical 696 to 826 ms21:25-21:30 UTC: 26 of 26 places loaded it, typical 885 ms21:30-21:45 UTC: 35 of 35 places loaded it, typical 682 to 842 ms21:45-21:50 UTC: 33 of 33 places loaded it, typical 668 ms21:50-21:55 UTC: 25 of 25 places loaded it, typical 883 ms21:55-22:05 UTC: 35 of 35 places loaded it, typical 620 to 774 ms22:05-22:10 UTC: 32 of 32 places loaded it, typical 755 ms22:10-09:15 UTC: 35 of 35 places loaded it, typical 551 to 863 ms09:15-09:20 UTC: 32 of 32 places loaded it, typical 771 ms09:20-20:40 UTC: 35 of 35 places loaded it, typical 535 to 892 ms20:40-20:45 UTC: 7 of 7 places loaded it, typical 510 ms Typical response time of the places that loaded it, at most 908 ms

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

Tinted columns: when Red Hat's status page showed a partial outage, a major outage or maintenance, as we read it every 2.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded redhat.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Fr. S. Antarctic Lands only.

Latest checks, 20:40-20:45 UTC: 7 of 7 places loaded it, typical 510 ms.

Report totals as of 7 Nov, 20:41 UTC

Report a problem with Red Hat

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 Fr. S. Antarctic Lands

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 Fr. S. Antarctic Lands. The report chart above is filtered to Fr. S. Antarctic Lands.

Our own checks of redhat.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Seoul: loaded in 1289 ms Dallas: loaded in 424 ms Querétaro: loaded in 379 ms Cape Town: loaded in 1249 ms Atlanta: loaded in 101 ms Frankfurt: loaded in 510 ms Delhi: loaded in 1240 ms São Paulo: loaded in 540 ms Lauterbourg: loaded in 544 ms Mumbai: loaded in 1001 ms Amsterdam: loaded in 372 ms Madrid: loaded in 472 ms Seattle: loaded in 330 ms Portsmouth: loaded in 396 ms New York: loaded in 141 ms London: loaded in 374 ms Tokyo: loaded in 656 ms Bangalore: loaded in 1218 ms Johannesburg: loaded in 937 ms Toronto: loaded in 145 ms Port Louis: loaded in 1483 ms Doha: loaded in 1377 ms Tel Aviv: loaded in 1095 ms Warsaw: loaded in 504 ms Melbourne: loaded in 903 ms St. Louis: loaded in 236 ms Singapore: loaded in 1024 ms Jakarta: loaded in 949 ms Santiago: loaded in 524 ms Osaka: loaded in 822 ms Los Angeles: loaded in 754 ms New Jersey: loaded in 324 ms Hamina: loaded in 489 ms Hong Kong: loaded in 844 ms Sydney: loaded in 1186 ms
  • SeoulReachable1289 ms, just now
  • DallasReachable424 ms, just now
  • QuerétaroReachable379 ms, just now
  • Cape TownReachable1249 ms, just now
  • AtlantaReachable101 ms, just now
  • FrankfurtReachable510 ms, just now
  • DelhiReachable1240 ms, just now
  • São PauloReachable540 ms, 3 min ago
  • LauterbourgReachable544 ms, 3 min ago
  • MumbaiReachable1001 ms, 3 min ago
  • AmsterdamReachable372 ms, 4 min ago
  • MadridReachable472 ms, 4 min ago
  • SeattleReachable330 ms, 4 min ago
  • PortsmouthReachable396 ms, 4 min ago
  • New YorkReachable141 ms, 4 min ago
  • LondonReachable374 ms, 4 min ago
  • TokyoReachable656 ms, 4 min ago
  • BangaloreReachable1218 ms, 4 min ago
  • JohannesburgReachable937 ms, 4 min ago
  • TorontoReachable145 ms, 4 min ago
  • Port LouisReachable1483 ms, 4 min ago
  • DohaReachable1377 ms, 4 min ago
  • Tel AvivReachable1095 ms, 4 min ago
  • WarsawReachable504 ms, 4 min ago
  • MelbourneReachable903 ms, 4 min ago
  • St. LouisReachable236 ms, 4 min ago
  • SingaporeReachable1024 ms, 4 min ago
  • JakartaReachable949 ms, 5 min ago
  • SantiagoReachable524 ms, 5 min ago
  • OsakaReachable822 ms, 5 min ago
  • Los AngelesReachable754 ms, 5 min ago
  • New JerseyReachable324 ms, 5 min ago
  • HaminaReachable489 ms, 5 min ago
  • Hong KongReachable844 ms, 5 min ago
  • SydneyReachable1186 ms, 5 min ago

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

Parts of Red Hat

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, 12:12 UTC, partial outage for 12 min (1 of 119 parts affected: docs.redhat.com / Homepage).

Last 9030 days

54.34% 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

Recent problems

6 Nov, 12:12 UTCPartial outage12 min1 of 119 parts affected: docs.redhat.com / Homepage
6 Nov, 11:46 UTCPartial outage19 min1 of 119 parts affected: docs.redhat.com / Product Hub
6 Nov, 11:23 UTCPartial outage5 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:56 UTCPartial outage7 min1 of 119 parts affected: docs.redhat.com / Content
6 Nov, 10:06 UTCPartial outage34 min1 of 119 parts affected: docs.redhat.com / Product Hub
6 Nov, 09:58 UTCPartial outage4 min1 of 119 parts affected: docs.redhat.com / Product Hub
5 Nov, 11:39 UTCPartial outage7 h 1 minOpen incident: Docs.redhat.com - Intermittent performance degradation
5 Nov, 11:18 UTCPartial outage15 min2 of 119 parts affected: docs.redhat.com / Content, docs.redhat.com / Homepage
5 Nov, 10:27 UTCPartial outage3 min1 of 119 parts affected: docs.redhat.com / Product Hub
What can I try?

Having trouble with Red Hat?

  1. Compare reports from Fr. S. Antarctic Lands 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 Red Hat down, or is it just me?

Red Hat 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 Red Hat status page and load redhat.com 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 2.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.

Other services in Cloud and hosting

Each card shows that service's own status, not Red Hat's. A problem listed here does not mean Red Hat has one.

See the live outage feed for Fr. S. Antarctic Lands · Find another service