Metronome incident

Increased lag for notifications and API

Minor Resolved View vendor source →

Metronome experienced a minor incident on February 23, 2026 affecting Overall and Alerts, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 11:25 PM UTC
Resolved
Feb 23, 2026, 11:25 PM UTC
Duration
Detected by Pingoru
Feb 23, 2026, 11:25 PM UTC

Affected components

OverallAlerts

Update timeline

  1. investigating Feb 23, 2026, 03:35 PM UTC

    Status: Investigating We have identified an issue within our notification system and api which is causing increased lag. We are taking steps now to remediate the issue. Affected components Overall (Degraded performance) Alerts (Degraded performance)

  2. monitoring Feb 23, 2026, 08:05 PM UTC

    Status: Monitoring We've identified the root cause in our usage system and have performed several mitigations. We continue to monitor the stability of the system and are working to enact further mitigations to prevent a recurrence of these issues. Affected components Alerts (Operational) Overall (Operational)

  3. resolved Feb 23, 2026, 11:25 PM UTC

    Status: Resolved We successfully audited our mitigations for the problematic workload and feel good about the stability of our system. We are acting on further mitigations to better detect and prevent similar problems in the future. Affected components Overall (Operational) Alerts (Operational)