Metronome Outage History

Metronome is up right now

Metronome had 22 outages in the last 2 years totaling 6h 37m of downtime — averaging 0.9 incidents per month.

There were 22 Metronome outages since December 7, 2025 totaling 6h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.metronome.com

Minor May 28, 2026

Elevated API Errors and Latency

Detected by Pingoru
May 28, 2026, 06:21 AM UTC
Resolved
May 28, 2026, 06:21 AM UTC
Duration
—
Affected: OverallDashboardEmbeddable DashboardsAlerts
Timeline · 2 updates
  1. monitoring May 28, 2026, 04:50 AM UTC

    Status: Monitoring We are seeing a recurrence of the issue impacting API performance. We have applied a mitigation and are monitoring recovery. Affected components Dashboard (Degraded performance) Overall (Degraded performance) Alerts (Degraded performance) Embeddable Dashboards (Degraded performance)

  2. resolved May 28, 2026, 06:21 AM UTC

    Status: Resolved API has again remained stable and this situation should be resolved. We're continuing to monitor to see if this occurs again. Affected components Dashboard (Operational) Overall (Operational) Alerts (Operational) Embeddable Dashboards (Operational)

Read the full incident report →

Minor May 8, 2026

Delayed Alerts

Detected by Pingoru
May 08, 2026, 01:03 AM UTC
Resolved
May 08, 2026, 01:03 AM UTC
Duration
—
Affected: Alerts
Timeline · 2 updates
  1. monitoring May 07, 2026, 08:05 PM UTC

    Status: Monitoring Between 19:12 and 19:42UTC, we experienced a technical issue that caused delays in outgoing notifications. This resulted in a temporary backlog of messages. We have since processed the backlog, and all delayed notifications have been successfully delivered. Affected components Alerts (Degraded performance)

  2. resolved May 08, 2026, 01:03 AM UTC

    Status: Resolved All systems are operational. The earlier delays affecting alerts have been resolved, and all notifications are being delivered as expected. Affected components Alerts (Operational)

Read the full incident report →

Minor May 2, 2026

Delayed/Unavailable Alerts

Detected by Pingoru
May 02, 2026, 06:04 AM UTC
Resolved
May 02, 2026, 06:04 AM UTC
Duration
—
Affected: OverallAlerts
Timeline · 5 updates
  1. investigating May 02, 2026, 01:21 AM UTC

    Status: Investigating Metronome's API is experiencing availability issues across all endpoints. We are actively working to remediate the issue. Affected components Overall (Partial outage)

  2. resolved May 02, 2026, 02:47 AM UTC

    Status: Resolved API has remained stable and this situation has resolved. The time window of errors was from 00:38 UTC - 01:12 UTC. Affected components Overall (Operational)

  3. identified May 02, 2026, 04:19 AM UTC

    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)

  4. monitoring May 02, 2026, 05:31 AM UTC

    Status: Monitoring The underlying issue delaying alerts has been resolved. We are going through the alerts backlog and will continue to monitor. Affected components Overall (Operational) Alerts (Degraded performance)

  5. resolved May 02, 2026, 06:04 AM UTC

    Status: Resolved Alerts backlog has been processed and this situation has resolved. Affected components Overall (Operational) Alerts (Operational)

Read the full incident report →

Minor April 19, 2026

Elevated API error rate

Detected by Pingoru
Apr 19, 2026, 08:54 AM UTC
Resolved
Apr 19, 2026, 08:54 AM UTC
Duration
—
Affected: Overall
Timeline · 2 updates
  1. monitoring Apr 19, 2026, 08:51 AM UTC

    Status: Monitoring The Metronome team noticed elevated error rates across a number of API endpoints between 08:54 UTC and 09:04 UTC on April 19 2026. We're continuing to monitor the situation. Affected components Overall (Degraded performance)

  2. resolved Apr 19, 2026, 08:54 AM UTC

    Status: Resolved The issue has resolved. We're monitoring the situation. Affected components Overall (Operational)

Read the full incident report →

Minor April 6, 2026

Investigating delay creating new billable metrics

Detected by Pingoru
Apr 06, 2026, 07:15 PM UTC
Resolved
Apr 06, 2026, 07:15 PM UTC
Duration
—
Affected: Usage Pipeline
Timeline · 2 updates
  1. investigating Apr 06, 2026, 06:55 PM UTC

    Status: Investigating We are investigating the delay in matching events matching new billable metrics starting from 17:44UTC. At this time, we do not believe this incident impacts any existing billable metrics created prior. We will share more details as we confirm the root cause and mitigate. Affected components Usage Pipeline (Degraded performance)

  2. resolved Apr 06, 2026, 07:15 PM UTC

    Status: Resolved All billable metrics have been created and are aggregating events normally, no further impact. Affected components Usage Pipeline (Operational)

Read the full incident report →

Minor April 3, 2026

Alerts and Notifications Delayed

Detected by Pingoru
Apr 03, 2026, 07:48 AM UTC
Resolved
Apr 03, 2026, 07:48 AM UTC
Duration
—
Affected: Alerts
Timeline · 8 updates
  1. identified Apr 02, 2026, 10:23 PM UTC

    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)

  2. identified Apr 02, 2026, 11:51 PM UTC

    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)

  3. identified Apr 03, 2026, 12:53 AM UTC

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

  4. identified Apr 03, 2026, 01:53 AM UTC

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

  5. identified Apr 03, 2026, 03:17 AM UTC

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

  6. identified Apr 03, 2026, 05:36 AM UTC

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

  7. monitoring Apr 03, 2026, 07:33 AM UTC

    Status: Monitoring All threshold notifications have now been sent. The team is verifying the remediations. Affected components Alerts (Operational)

  8. resolved Apr 03, 2026, 07:48 AM UTC

    Status: Resolved All notifications have been sent. Affected components Alerts (Operational)

Read the full incident report →

Minor March 27, 2026

API Degradation

Detected by Pingoru
Mar 27, 2026, 11:08 PM UTC
Resolved
Mar 27, 2026, 11:08 PM UTC
Duration
—
Affected: Overall
Timeline · 2 updates
  1. identified Mar 27, 2026, 10:51 PM UTC

    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)

  2. resolved Mar 27, 2026, 11:08 PM UTC

    Status: Resolved The mitigation is complete. Impact spanned 22:31 - 22:57 UTC. Affected components Overall (Operational)

Read the full incident report →

Minor March 18, 2026

Notifications and alerts are delayed

Detected by Pingoru
Mar 18, 2026, 12:03 AM UTC
Resolved
Mar 18, 2026, 12:03 AM UTC
Duration
—
Affected: Alerts
Timeline · 4 updates
  1. investigating Mar 17, 2026, 08:31 PM UTC

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

  2. identified Mar 17, 2026, 09:28 PM UTC

    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)

  3. monitoring Mar 17, 2026, 10:23 PM UTC

    Status: Monitoring We have deployed a fix and the latencies have been stable since 21:40 UTC. We are continuing to monitor the situation. Affected components Alerts (Operational)

  4. resolved Mar 18, 2026, 12:03 AM UTC

    Status: Resolved We have been monitoring the issue and confirmed it has resolved. Affected components Alerts (Operational)

Read the full incident report →

Minor March 14, 2026

Re-enabling previously unsuccessful threshold billing configurations degraded

Detected by Pingoru
Mar 14, 2026, 04:01 AM UTC
Resolved
Mar 14, 2026, 04:01 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 11, 2026, 11:36 PM UTC

    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.

  2. monitoring Mar 12, 2026, 07:44 PM UTC

    Status: Monitoring We have deployed the remaining fix for spend threshold billing configurations. Clients are now fully able to re-enable threshold billing configurations through the API.

  3. resolved Mar 14, 2026, 04:01 AM UTC

    Status: Resolved We have identified all affected customers from this incident. If you have been impacted, a Metronome representative will reach out.

Read the full incident report →

Minor March 2, 2026

Delays in Contract Data Export

Detected by Pingoru
Mar 02, 2026, 11:50 PM UTC
Resolved
Mar 02, 2026, 11:50 PM UTC
Duration
—
Affected: Data Export
Timeline · 3 updates
  1. investigating Mar 02, 2026, 09:03 PM UTC

    Status: Investigating We are experiencing delays in our contract data export pipelines, which may result in delayed data since 2/28 for some clients. We are investigating the issue. Affected components Data Export (Partial outage)

  2. identified Mar 02, 2026, 11:16 PM UTC

    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)

  3. resolved Mar 02, 2026, 11:50 PM UTC

    Status: Resolved Contract data export and the resulting transfers are now complete. Affected components Data Export (Operational)

Read the full incident report →

Minor March 2, 2026

Delays to alerts triggered by Pricing & Packaging changes

Detected by Pingoru
Mar 02, 2026, 03:28 AM UTC
Resolved
Mar 02, 2026, 03:28 AM UTC
Duration
—
Affected: Alerts
Timeline · 3 updates
  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)

Read the full incident report →

Minor March 2, 2026

Elevated API Latencies

Detected by Pingoru
Mar 02, 2026, 12:25 AM UTC
Resolved
Mar 02, 2026, 12:25 AM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Mar 01, 2026, 09:13 PM UTC

    Status: Monitoring Metronome had elevated API latencies from 12:25 - 20:25 UTC for contracts and invoicing endpoints. This has since been resolved.

  2. resolved Mar 02, 2026, 12:25 AM UTC

    Status: Resolved Elevated API latencies affecting contracts and invoicing endpoints have been mitigated. Service is operating normally as of 20:25 UTC.

Read the full incident report →

Minor March 1, 2026

Increased latency for offset notifications

Detected by Pingoru
Mar 01, 2026, 03:32 PM UTC
Resolved
Mar 01, 2026, 03:32 PM UTC
Duration
—
Affected: Alerts
Timeline · 3 updates
  1. identified Feb 28, 2026, 08:44 PM UTC

    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)

  2. monitoring Mar 01, 2026, 01:58 AM UTC

    Status: Monitoring The fix has been deployed, we will be monitoring overnight. Affected components Alerts (Operational)

  3. resolved Mar 01, 2026, 03:32 PM UTC

    Status: Resolved We have monitored the fix overnight and the issue didn't recur. Affected components Alerts (Operational)

Read the full incident report →

Minor February 23, 2026

Increased lag for notifications and API

Detected by Pingoru
Feb 23, 2026, 11:25 PM UTC
Resolved
Feb 23, 2026, 11:25 PM UTC
Duration
—
Affected: OverallAlerts
Timeline · 3 updates
  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)

Read the full incident report →

Minor February 18, 2026

Elevated API and Alert Errors

Detected by Pingoru
Feb 18, 2026, 08:45 PM UTC
Resolved
Feb 18, 2026, 08:45 PM UTC
Duration
—
Affected: OverallAlerts
Timeline · 3 updates
  1. investigating Feb 18, 2026, 06:41 PM UTC

    Status: Investigating We are experiencing an elevated rate of API errors, we are currently investigating the issue. Affected components Overall (Degraded performance)

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

    Status: Monitoring We have identified the issue and it's now resolved. The API is back to normal. We also identified that the alerts system was affected and we are currently reflowing any alerts that may have been delayed. Affected components Overall (Operational) Alerts (Degraded performance)

  3. resolved Feb 18, 2026, 08:45 PM UTC

    Status: Resolved API and Alerts traffic is now back to normal Affected components Overall (Operational) Alerts (Operational)

Read the full incident report →

Minor February 11, 2026

Increased API Latency & Errors

Detected by Pingoru
Feb 11, 2026, 04:52 PM UTC
Resolved
Feb 11, 2026, 04:52 PM UTC
Duration
—
Affected: Overall
Timeline · 2 updates
  1. investigating Feb 11, 2026, 04:51 PM UTC

    Status: Investigating From ~16:11-16:14 UTC we had an incident affecting API error rates. Error rates remained slightly elevated until 16:51 UTC. The ingest API was not affected. Affected components Overall (Degraded performance)

  2. resolved Feb 11, 2026, 04:52 PM UTC

    Status: Resolved This issue has been resolved. Affected components Overall (Operational)

Read the full incident report →

Minor February 8, 2026

Future Dated System Notifications Delayed

Detected by Pingoru
Feb 08, 2026, 10:35 AM UTC
Resolved
Feb 08, 2026, 10:35 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 08, 2026, 09:35 AM UTC

    Status: Investigating We've identified an issue with future-dated System Notifications not being delivered.

  2. investigating Feb 08, 2026, 10:30 AM UTC

    Status: Investigating This underlying issue is now resolved and are processing the missed notifications now.

  3. resolved Feb 08, 2026, 10:35 AM UTC

    Status: Resolved All System Notifications should now be delivered via webhooks.

Read the full incident report →

Minor February 8, 2026

Azure marketplaces service degradation

Detected by Pingoru
Feb 08, 2026, 06:23 AM UTC
Resolved
Feb 08, 2026, 06:23 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Feb 07, 2026, 09:24 AM UTC

    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.

  2. monitoring Feb 07, 2026, 04:47 PM UTC

    Status: Monitoring Azure's service degradation has begun recovery, and we will continue to monitor as it progresses. The degradation has been limited to customers using Azure's West US region.

  3. resolved Feb 08, 2026, 06:23 AM UTC

    Status: Resolved Azure marketplaces services have fully recovered, and metering has resumed. No data loss is expected, and no further action is required.

Read the full incident report →

Minor February 6, 2026

Increased lag for webhook notifications

Detected by Pingoru
Feb 06, 2026, 06:46 PM UTC
Resolved
Feb 06, 2026, 06:46 PM UTC
Duration
—
Affected: Alerts
Timeline · 3 updates
  1. identified Feb 05, 2026, 09:49 PM UTC

    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)

  2. monitoring Feb 06, 2026, 01:59 AM UTC

    Status: Monitoring Webhook delivery delays have been cleared and processing is back to normal. We’ll continue monitoring to ensure stability. Affected components Alerts (Operational)

  3. resolved Feb 06, 2026, 06:46 PM UTC

    Status: Resolved Latencies have remained normal overnight. The issue has been resolved. Affected components Alerts (Operational)

Read the full incident report →