Metronome incident

Ingest and Alerts are delayed

Minor Resolved View vendor source →

Metronome experienced a minor incident on January 29, 2026 affecting Usage Pipeline and Alerts, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2026, 09:17 PM UTC
Resolved
Jan 29, 2026, 09:17 PM UTC
Duration
Detected by Pingoru
Jan 29, 2026, 09:17 PM UTC

Affected components

Usage PipelineAlerts

Update timeline

  1. identified Jan 23, 2026, 11:30 PM UTC

    Status: Identified We are investigating an increase in aggregation time, which is impacting both the usage pipeline and alert evaluation time. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  2. identified Jan 24, 2026, 12:36 AM UTC

    Status: Identified We are investigating an increase in aggregation time, which is impacting both the usage pipeline and alert evaluation time. Ingest availability is not impacted. Invoice finalization has been paused to ensure data integrity. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  3. identified Jan 24, 2026, 01:37 AM UTC

    Status: Identified We are investigating an increase in aggregation time, which is impacting both the usage pipeline and alert evaluation time, for a subset of usage events. Ingest availability is not impacted. Invoice finalization and threshold billing has been paused to ensure data integrity. Affected components Usage Pipeline (Partial outage) Alerts (Partial outage)

  4. identified Jan 24, 2026, 04:25 AM UTC

    Status: Identified We have mitigated an increase in aggregation time for a subset of usage events. Notifications remain delayed for a subset of customers. Invoice finalization and threshold billing remain paused. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  5. identified Jan 24, 2026, 06:18 AM UTC

    Status: Identified We have mitigated an increase in aggregation time for a subset of usage events. Notifications remain delayed for a subset of customers but delay is decreasing. Invoice finalization and threshold billing remain paused until data integrity checks complete. The team will be running data integrity checks overnight. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  6. identified Jan 24, 2026, 05:18 PM UTC

    Status: Identified We have identified an issue with our mitigation for aggregation and are working on resolving that issue. Aggregation time remains delayed for data ingested between 1/23 16UTC and 1/24 12UTC. Notifications remain delayed as well. Invoice finalization and threshold billing remain paused until remediation and data integrity checks complete successfully. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  7. identified Jan 25, 2026, 09:40 AM UTC

    Status: Identified Aggregations and notifications are caught up. We are repeating our data quality checks to ensure correctness of invoices. Invoice finalization and threshold billing remain paused until data integrity checks complete successfully. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  8. identified Jan 25, 2026, 05:59 PM UTC

    Status: Identified Threshold billing is unpaused. Aggregations and notifications are caught up. Invoice finalization remains paused. Ingest availability is not impacted. Affected components Alerts (Partial outage) Usage Pipeline (Partial outage)

  9. monitoring Jan 25, 2026, 09:23 PM UTC

    Status: Monitoring All issues have been mitigated, and the team is now monitoring. Affected components Alerts (Operational) Usage Pipeline (Operational)

  10. resolved Jan 29, 2026, 09:17 PM UTC

    Status: Resolved This issue has been resolved. Affected components Alerts (Operational) Usage Pipeline (Operational)