Metronome Outage History

Metronome is up right now

Pingoru has recorded 68 incidents for Metronome: 68 in the last 12 months and 14 in the last 90 days.

Source: status.metronome.com

68incidents recorded
68last 12 months
14last 90 days
11 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct6
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking Metronome in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026814 of 720 (2%)
May 2026413 of 744 (2%)
June 202600 of 720 (0%)
July 2026836 of 744 (5%)
August 202600 of 744 (0%)
September 2026626 of 720 (4%)
October 2026618 of 589 (3%)

Incidents, newest first

Minor March 17, 2026 Notifications and alerts are delayed 3h 31m Alerts

Started Mar 17, 2026, 08:31 PM UTC· resolved Mar 18, 2026, 12:03 AM UTC

  1. investigating Mar 17, 2026, 08:31 PM UTC

    Notifications and alerts are experiencing sporadic delays. There's no impact to ingestion at this time. The team is investigating.

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

    Notifications and alerts are continuing to experience sporadic delays. There's no impact to ingestion at this time. The team is actively investigating.

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

    We have deployed a fix and the latencies have been stable since 21:40 UTC. We are continuing to monitor the situation.

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

    We have been monitoring the issue and confirmed it has resolved.

Read the full incident report →

Minor March 11, 2026 Re-enabling previously unsuccessful threshold billing configurations degraded 2d 4h

Started Mar 11, 2026, 11:36 PM UTC· resolved Mar 14, 2026, 04:01 AM UTC

  1. identified Mar 11, 2026, 11:36 PM UTC

    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

    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

    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 2h 47m Data Export

Started Mar 02, 2026, 09:03 PM UTC· resolved Mar 02, 2026, 11:50 PM UTC

  1. investigating Mar 02, 2026, 09:03 PM UTC

    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.

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

    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.

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

    Contract data export and the resulting transfers are now complete.

Read the full incident report →

Minor March 1, 2026 Elevated API Latencies 3h 12m

Started Mar 01, 2026, 09:13 PM UTC· resolved Mar 02, 2026, 12:25 AM UTC

  1. monitoring Mar 01, 2026, 09:13 PM UTC

    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

    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 →

Major March 1, 2026 Delays to alerts triggered by Pricing & Packaging changes 7h 36m

Started Mar 01, 2026, 07:52 PM UTC· resolved Mar 02, 2026, 03:28 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 28, 2026 Increased latency for offset notifications 18h 48m Alerts

Started Feb 28, 2026, 08:44 PM UTC· resolved Mar 01, 2026, 03:32 PM UTC

  1. identified Feb 28, 2026, 08:44 PM UTC

    We have identified increased latency in our offset notification system. We have identified the issue and are applying a fix.

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

    The fix has been deployed, we will be monitoring overnight.

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

    We have monitored the fix overnight and the issue didn't recur.

Read the full incident report →

Minor February 23, 2026 Increased lag for notifications and API 7h 50m Overall, Alerts

Started Feb 23, 2026, 03:35 PM UTC· resolved Feb 23, 2026, 11:25 PM UTC

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

    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.

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

    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.

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

    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.

Read the full incident report →

Minor February 18, 2026 Elevated API and Alert Errors 2h 4m Overall, Alerts

Started Feb 18, 2026, 06:41 PM UTC· resolved Feb 18, 2026, 08:45 PM UTC

  1. investigating Feb 18, 2026, 06:41 PM UTC

    We are experiencing an elevated rate of API errors, we are currently investigating the issue.

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

    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.

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

    API and Alerts traffic is now back to normal

Read the full incident report →

Minor February 11, 2026 Increased API Latency & Errors 41s Overall

Started Feb 11, 2026, 04:51 PM UTC· resolved Feb 11, 2026, 04:52 PM UTC

  1. investigating Feb 11, 2026, 04:51 PM UTC

    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.

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

    This issue has been resolved.

Read the full incident report →

Minor February 8, 2026 Future Dated System Notifications Delayed 59m

Started Feb 08, 2026, 09:35 AM UTC· resolved Feb 08, 2026, 10:35 AM UTC

  1. investigating Feb 08, 2026, 09:35 AM UTC

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

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

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

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

    All System Notifications should now be delivered via webhooks.

Read the full incident report →

Minor February 7, 2026 Azure marketplaces service degradation 20h 58m

Started Feb 07, 2026, 09:24 AM UTC· resolved Feb 08, 2026, 06:23 AM UTC

  1. identified Feb 07, 2026, 09:24 AM UTC

    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

    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

    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 5, 2026 Increased lag for webhook notifications 20h 57m Alerts

Started Feb 05, 2026, 09:49 PM UTC· resolved Feb 06, 2026, 06:46 PM UTC

  1. identified Feb 05, 2026, 09:49 PM UTC

    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.

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

    Webhook delivery delays have been cleared and processing is back to normal. We’ll continue monitoring to ensure stability.

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

    Latencies have remained normal overnight. The issue has been resolved.

Read the full incident report →

Minor January 6, 2026 Delays in Data Export 4h 52m

Started Jan 06, 2026, 03:32 PM UTC· resolved Jan 06, 2026, 08:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Notice December 22, 2025 Delay in sending invoices to Stripe 1h 45m

Started Dec 22, 2025, 08:16 PM UTC· resolved Dec 22, 2025, 10:01 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →