How to Subscribe to Red Hat Status Incident Notifications

Updated

You can subscribe to Red Hat Status alerts by email or text message directly from status.redhat.com. Email subscriptions require an email address plus a one-time password (OTP) verification; text message subscriptions require selecting a country code and entering a phone number. Once subscribed, you receive notifications whenever Red Hat creates, updates, or resolves an incident.

Subscribe by Email

  1. Open status.redhat.com and locate the Subscribe to Updates section (the page heading for this form is "Subscribe to Incident").
  2. Enter your email address in the Email address field.
  3. Request the OTP, then enter it in the Enter OTP field to verify.
  4. If the code doesn't arrive, use Resend OTP; the form shows a countdown ("Resend OTP in: seconds") before you can request another.

Expected result: your email is registered and you'll get a message whenever Red Hat creates, updates, or resolves an incident.

Note that the form is protected by reCAPTCHA, so you must complete that check before the OTP step will succeed.

Subscribe by Text Message

  1. In the text message notification section, open the Country code dropdown and select your country (for example, United States +1, United Kingdom +44, Germany +49, India +91, Japan +81, China +86).
  2. Enter your phone number.
  3. Complete the subscription so texts are sent whenever Red Hat creates or resolves an incident.

One difference worth knowing: the email option covers creates, updates, and resolutions, while the text option is described as covering creates and resolutions.

What You'll Be Notified About

Channel Triggers
Email Incident created, updated, or resolved
Text message Incident created or resolved

Checking Past Incidents

The page also includes a Past Incidents section with historical data on system performance, so you can review earlier events without waiting for a notification.

Common Snags

  • No OTP received: wait for the resend countdown to finish, then use Resend OTP; check spam or junk folders for the email.
  • Wrong country code: the dropdown is long and alphabetical, so confirm the dialing code matches your number before submitting.
  • reCAPTCHA failure: the form won't proceed until the reCAPTCHA check passes; reload the page and try again if it stalls.

If you only need a quick check rather than ongoing alerts, the live status and Past Incidents list on the site may be enough; subscribe when you want to be told about incidents without visiting the page.