Quay incident
Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values
Resolved after 13 days, affecting Subscription Watch, on April 3, 2026.
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
Affected components
Update timeline
- identified Apr 03, 2026, 02:04 PM UTC
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.
- identified Apr 03, 2026, 02:34 PM UTC
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
- resolved Apr 16, 2026, 02:33 PM UTC
The notifications for non-payg should work correctly.
Your product runs on more than Quay
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services