Metronome incident

Delays to alerts triggered by Pricing & Packaging changes

Minor Resolved View vendor source →
Started
Mar 02, 2026, 03:28 AM UTC
Resolved
Mar 02, 2026, 03:28 AM UTC
Duration
Detected by Pingoru
Mar 02, 2026, 03:28 AM UTC

Affected components

Alerts

Update timeline

  1. identified Mar 01, 2026, 06:30 PM UTC

    Status: Identified We have identified a problem in our infrastructure that is delaying alert triggers when a customer's pricing and packaging is mutated. This includes (but is not limited to) commit purchases and contract changes. Impact began at approximately 18:30 UTC. As part of our remediation, all affected customers will have their configured alerts evaluated. Customers actively receiving usage are operating as normal with alerts being evaluated. Affected components Alerts (Partial outage)

  2. monitoring Mar 01, 2026, 08:18 PM UTC

    Status: Monitoring Our mitigation was successful and alerts are now processed for the affected customers. Clients may see webhooks from alarms that were delayed in this time window. Affected components Alerts (Operational)

  3. resolved Mar 02, 2026, 03:28 AM UTC

    Status: Resolved We've monitored our mitigation and do not foresee risk of future issues. Affected components Alerts (Operational)

Looking to track Metronome downtime and outages?

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

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

5 free monitors · No credit card required