What is Red Hat Status?
Updated
Red Hat Status (status.redhat.com) is Red Hat's official status page for real-time and historical data on system performance. Use it when you need to check whether a Red Hat service is currently experiencing an incident, review how past incidents were resolved, or subscribe to email or text message notifications so you learn about new incidents without refreshing the page.
What the page provides
The page is built around two kinds of information:
- Current incidents — active problems affecting Red Hat services, which the page describes as being created, updated, and resolved over time.
- Past Incidents — a historical record you can review to see what happened previously and how an issue progressed.
The site describes itself as the home for real-time and historical data on system performance, so it serves both as a live check and as a reference for past reliability.
Subscribing to incident updates
The page offers two notification channels, both driven by the "Subscribe to Incident" / "Subscribe to Updates" flow.
Email notifications
- Enter your email address in the subscription form.
- The page sends a one-time password (OTP); enter it in the "Enter OTP" field.
- If the code doesn't arrive, use "Resend OTP" — the page shows a countdown ("Resend OTP in: seconds") before you can request another.
Once confirmed, you receive an email whenever Red Hat creates, updates, or resolves an incident.
Text message notifications
- Select your country code from the dropdown (the list covers codes from Afghanistan (+93) through a wide range of countries, including China (+86), India (+91), and the United States (+1)).
- Enter your phone number and complete the verification step.
Text alerts are sent when Red Hat creates or resolves an incident — note this is a narrower trigger than email, which also covers updates.
The form is protected by reCAPTCHA, and Google's Privacy Policy and Terms of Service apply to that verification step.
Email vs. text: which to choose
| Text message | ||
|---|---|---|
| Trigger | Incident created, updated, or resolved | Incident created or resolved |
| Best for | Following the full lifecycle of an incident, including progress updates | Getting a fast heads-up that something started or is over |
| Setup | Email address + OTP | Country code + phone number verification |
Choose email if you want to track how an incident evolves; choose text if you mainly need to know the moment something breaks or is fixed. You can use both.
Practical tips
- Check Past Incidents before reporting a problem — a recurring issue may already have a documented history and resolution pattern.
- Keep the OTP step in mind — if you're subscribing during an active incident, the verification email may take a moment; the resend countdown tells you when to try again.
- Pick the right country code first for text alerts; the dropdown is long, so scroll to your country rather than assuming a default.
What it doesn't tell you
The page is a status and notification service. The available information does not describe pricing, plan entitlements, or support-case handling, so for account-specific issues you'll still need Red Hat's support channels rather than the status page alone.