Metronome Outage History

Status: Identified Some of our alerts are delayed or unavailable due to infrastructure issues. Usage related alerts are not affected. We're actively working to restore our alerts. Affected components Overall (Operational) Alerts (Degraded performance)

Status: Identified Alerts and notifications between 19:05 -> 21:50 UTC are delayed. Ingest and API are not impacted at this time. Affected components Alerts (Partial outage)

Status: Identified Alerts and notifications between 19:05 -> 21:50 UTC are delayed. The team is working on sending the impacted notifications at this time. All notifications after 21:50 UTC were processed normally. Ingest and API are not impacted. Affected components Alerts (Partial outage)

Status: Identified The team is still working on sending the impacted notifications at this time. Affected components Alerts (Partial outage)

Status: Identified The team is still working on sending impacted notifications at this time. Affected components Alerts (Partial outage)

Status: Identified The team has resent several notification types and is currently working on resending threshold notifications. Affected components Alerts (Partial outage)

Status: Identified The team is still in the process of resending threshold notifications and working through the backlog. Affected components Alerts (Partial outage)

Status: Identified Metronome is experiencing an API outage that is primarily affecting retrieval of invoices and contracts. Ingest is not impacted at this time. Impact began at 22:31 UTC. We are actively working on the mitigation. Affected components Overall (Degraded performance)

Status: Identified Notifications and alerts are continuing to experience sporadic delays. There's no impact to ingestion at this time. The team is actively investigating. Affected components Alerts (Degraded performance)

Status: Identified When a previously unsuccessful threshold billing configuration on a contract is re-enabled via the v2/contracts/edit API, the configuration does not get enabled. Re-enabling performed through the frontend is confirmed to be working as expected. This affects re-enabling attempts via the API since 3/1/2026. We are currently deploying a fix for credit balance threshold configurations, and will fast-follow with a fix for spend threshold configurations.

Status: Identified We've identified the root cause of the issue and have initiated a manual contract data export run. We expect this to take several hours to complete and data will be uploaded as soon as it is available. Affected components Data Export (Partial outage)

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)

Status: Identified We have identified increased latency in our offset notification system. We have identified the issue and are applying a fix. Affected components Alerts (Degraded performance)

Status: Identified We are aware of issues affecting metering of customer usage through Azure. We will continue to monitor Azure's outage and provide an update when it is clear. Once this happens, all customers will be metered appropriately for any usage during this outage.

Status: Identified We have identified an issue within our notification system which is causing increased lag for webhook sends. We are taking steps now to remediate the issue. Affected components Alerts (Degraded performance)