- Level
- confirmed
- Worst impact
- Degraded
- Components
- Subscription Watch
- Down Index
- 23of 100
What to do
Check whether you use Red Hat Subscription Watch. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 13d it lasted.
Anything that failed between 2026-04-03 14:04 UTC and 2026-04-16 14:33 UTC may need a replay.Subscribe to Red Hat's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=red-hat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Red Hat 3
- identified
Backend service responsible of checking over usage condition is processing the wrong data for non-PAYGO products. This is leading to unexpected subscription threshold exceeded notifications with misleading values.
provider
- identified
We want customers to know that the notifications capability within Subscription Watch is currently turned off due to over usage notifications being sent out in error. Jira issue is https://redhat.atlassian.net/browse/SWATCH-4870
provider
- resolved
The notifications for non-payg should work correctly.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d675cc42e0
Is Red Hat still down?
No, this incident was resolved 2026-04-16 14:33 UTC. For Red Hat's live state, see https://down.guide/red-hat.
How long did it last?
13d, from 2026-04-03 14:04 UTC to 2026-04-16 14:33 UTC, by the times Red Hat posted.
What was affected?
Red Hat named Subscription Watch.
What caused it?
Red Hat hasn't published a root cause. If it does, it shows here.
Where does this come from?
Red Hat's official status page, https://status.redhat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.