Skip to main content

Is Red Hat Down?

No — Red Hat is up

Reachable from all 8 checked regions

Average response time: 1297ms

Last checked · checks run every 6 hours

Official status page: https://status.redhat.com

Red Hat uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
704ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

33-day clean streak
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks, 1 incident
Sep 15: 100.00% uptime, 32 checks, 1 incident
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 31 checks, 1 incident
Sep 21: 100.00% uptime, 31 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 31 checks
Sep 25: 100.00% uptime, 32 checks, 1 incident
Sep 26: 100.00% uptime, 46 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 31 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks, 1 incident
Oct 1: 100.00% uptime, 31 checks, 1 incident
Oct 2: 100.00% uptime, 32 checks, 1 incident
Oct 3: 100.00% uptime, 32 checks, 1 incident
Oct 4: 100.00% uptime, 32 checks, 1 incident
Oct 5: 100.00% uptime, 32 checks, 1 incident
Oct 6: 100.00% uptime, 32 checks, 1 incident
Oct 7: 100.00% uptime, 31 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 31 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 31 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
425ms
DNS 0ms TCP 22ms TLS 42ms TTFB 304ms
jnb
1076ms
DNS 0ms TCP 0ms TLS 2ms TTFB 1061ms
lax
444ms
DNS 0ms TCP 2ms TLS 5ms TTFB 412ms
lhr
229ms
DNS 0ms TCP 1ms TLS 4ms TTFB 213ms
nrt
1184ms
DNS 0ms TCP 50ms TLS 102ms TTFB 918ms
ord
418ms
DNS 0ms TCP 0ms TLS 3ms TTFB 402ms
sin
6265ms
DNS 0ms TCP 305ms TLS 649ms TTFB 2680ms
sjc
335ms
DNS 0ms TCP 1ms TLS 4ms TTFB 320ms

What Red Hat does

Red Hat sells enterprise open source software: Red Hat Enterprise Linux, OpenShift, Ansible Automation Platform and the subscription services around them. Its hosted estate is what running systems actually depend on, including the content delivery network that serves package updates, the entitlement service that authorises them, the container registries, and the Customer Portal where downloads and support cases live.

What an outage looks like

Package updates fail. dnf or yum stops partway with errors reaching cdn.redhat.com, or reports that a system is not entitled when the subscription service is unreachable. Container image pulls from registry.redhat.io fail during builds and deployments. The Customer Portal at access.redhat.com will not load, so knowledgebase articles, downloads and support cases are unavailable.

What to do about it

Read status.redhat.com, which lists components by hostname rather than by product. Check the specific host your error names: cdn.redhat.com and subscription.rhsm.redhat.com for updates and entitlement, registry.redhat.io for image pulls, access.redhat.com for the portal and support cases. Running systems and already-pulled containers are unaffected, so hold deployments rather than rebuilding.

Is it down for everyone, or just you?

If this page says Red Hat is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

IBM Cloud
IBM Cloud
GitHub
GitHub
GitLab
GitLab
N
npm

Red Hat outage FAQ

Why does dnf say my system is not entitled when the subscription is valid?
When subscription.rhsm.redhat.com or api.rhsm.redhat.com is unreachable, the entitlement check fails and the error reads like a subscription problem rather than a network one. Confirm under CDN and Entitlement Network on status.redhat.com before opening a support case or re-registering the host, because re-registering during an incident tends to make the state harder to unpick afterwards.
Does a Red Hat outage take my running servers down?
No. Red Hat's status page covers Red Hat's own hosted services, not the software already installed on your machines. Running RHEL systems, existing OpenShift clusters and containers already pulled keep working. What stops is anything that needs to reach Red Hat: updates, new image pulls, cluster provisioning through the console, and the support portal.
Can I still open a support case during an outage?
Not through the portal if access.redhat.com is affected, because Support Cases is one of its components. status.redhat.com lists Customer Service Webform, Support Cases and Start a Call as separate rows, so check which of those is actually down. Red Hat publishes incidents on its status page precisely because the usual support channel may be the unavailable thing.
Is Quay.io covered by Red Hat's status page?
Yes. Quay.io appears as its own component group on status.redhat.com, with API, Build System, Registry, Frontend and Security Scanning broken out separately. That matters if your builds pull from Quay rather than registry.redhat.io, because the two are distinct components and one can fail while the other serves images normally.
Does an outage affect OpenShift clusters I already run?
Existing clusters and the workloads on them keep running. What depends on Red Hat's hosted side is provisioning and lifecycle management through OpenShift Cluster Manager on console.redhat.com. Red Hat's own maintenance notices make the same distinction, stating that user workloads on existing clusters remain available while new clusters cannot be provisioned during the window.

How we measure this

  • We request Red Hat's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Red Hat publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Red Hat goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required