Quay incident

Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values

Notice Resolved View vendor source →
Started
Apr 03, 2026, 02:04 PM UTC
Resolved
Apr 16, 2026, 02:33 PM UTC
Duration
13d
Detected by Pingoru
Apr 03, 2026, 02:04 PM UTC

Affected components

Subscription Watch

Update timeline

  1. 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.

  2. 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

  3. resolved Apr 16, 2026, 02:33 PM UTC

    The notifications for non-payg should work correctly.

Looking to track Quay downtime and outages?

Pingoru polls Quay's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Quay reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Quay alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Quay for free

5 free monitors · No credit card required