Metronome Outage History

Metronome is up right now

Metronome had 38 outages in the last 2 years totaling 18h 18m of downtime — averaging 1.6 incidents per month.

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

Source: https://status.metronome.com

Minor October 8, 2026

Elevated API error rates

Detected by Pingoru
Oct 08, 2026, 06:53 PM UTC
Resolved
Oct 08, 2026, 10:13 PM UTC
Duration
3h 20m
Affected: Overall
Timeline · 3 updates
  1. monitoring Oct 08, 2026, 06:53 PM UTC

    Status: Monitoring We are investigating a burst of elevated API errors between 18:12-18:14 UTC. Ingest and alerts are not affected. Affected components Overall (Partial outage)

  2. monitoring Oct 08, 2026, 09:26 PM UTC

    Status: Monitoring We have mitigated the underlying issue. System metrics have returned to normal/healthy states. The team will continue to monitor but we believe the underlying cause has been addressed. Affected components Overall (Partial outage)

  3. resolved Oct 08, 2026, 10:13 PM UTC

    Status: Resolved API error rates are now stable. Affected components Overall (Operational)

Read the full incident report →

Minor October 3, 2026

Contract Data Export Delays

Detected by Pingoru
Oct 03, 2026, 04:52 AM UTC
Resolved
Oct 03, 2026, 11:46 AM UTC
Duration
6h 53m
Affected: Data Export
Timeline · 2 updates
  1. identified Oct 03, 2026, 04:52 AM UTC

    Status: Identified Some clients may be experiencing delays for contract-related data export tables. The impact is contained, and we are working to resync data for affected clients. We will provide updates as this progresses. Affected components Data Export (Degraded performance)

  2. resolved Oct 03, 2026, 11:46 AM UTC

    Status: Resolved Affected clients for earlier contract data export delays have been backfilled Affected components Data Export (Operational)

Read the full incident report →

Minor October 2, 2026

Delays in Data Exports

Detected by Pingoru
Oct 02, 2026, 04:05 PM UTC
Resolved
Oct 02, 2026, 07:51 PM UTC
Duration
3h 46m
Affected: Data Export
Timeline · 2 updates
  1. identified Oct 02, 2026, 04:05 PM UTC

    Status: Identified We are experiencing delays in our data export pipeline. The issue has been resolved, but exports will be delayed. Affected components Data Export (Degraded performance)

  2. resolved Oct 02, 2026, 07:51 PM UTC

    Status: Resolved All data exports have been transferred and are caught up. Affected components Data Export (Operational)

Read the full incident report →

Minor October 2, 2026

Delays in some Usage Invoices sending to Stripe

Detected by Pingoru
Oct 02, 2026, 02:49 PM UTC
Resolved
Oct 02, 2026, 07:08 PM UTC
Duration
4h 18m
Timeline · 2 updates
  1. investigating Oct 02, 2026, 02:49 PM UTC

    Status: Investigating We are observing delays in some usage invoices being sent to Stripe. Subscription invoices, prepaid balance thresholds, and spend thresholds are unaffected. We are actively investigating this.

  2. resolved Oct 02, 2026, 07:08 PM UTC

    Status: Resolved All impacted usage invoices have now successfully sent to Stripe

Read the full incident report →

Minor September 29, 2026

Invoice and line item data export tables delayed

Detected by Pingoru
Sep 29, 2026, 03:51 AM UTC
Resolved
Sep 29, 2026, 03:51 AM UTC
Duration
—
Affected: Data Export
Timeline · 3 updates
  1. investigating Sep 28, 2026, 03:45 PM UTC

    Status: Investigating We are investigating a delay of delivery of finalized invoices and line_items to client warehouses. We will report more details as we learn them. Other tables and datasets are not impacted. Affected components Data Export (Partial outage)

  2. monitoring Sep 28, 2026, 09:10 PM UTC

    Status: Monitoring Incremental transfers have been submitted to include data up until this morning. We expect to be caught up within the next couple hours on any data from today Affected components Data Export (Partial outage)

  3. resolved Sep 29, 2026, 03:51 AM UTC

    Status: Resolved We have completed the backfill and submitted transfers with current data Affected components Data Export (Operational)

Read the full incident report →

Minor September 12, 2026

Elevated API Error Rate

Detected by Pingoru
Sep 12, 2026, 01:37 AM UTC
Resolved
Sep 12, 2026, 01:37 AM UTC
Duration
—
Affected: OverallData ExportAlerts
Timeline · 4 updates
  1. investigating Sep 11, 2026, 11:22 PM UTC

    Status: Investigating We are investigating elevated API errors. Affected components Overall (Partial outage) Alerts (Partial outage) Data Export (Partial outage)

  2. monitoring Sep 11, 2026, 11:43 PM UTC

    Status: Monitoring We have mitigated the API error rates and are monitoring recovery. Affected components Overall (Degraded performance) Alerts (Degraded performance) Data Export (Partial outage)

  3. monitoring Sep 11, 2026, 11:52 PM UTC

    Status: Monitoring API error rates and other systems are showing normal/healthy metrics. Our team continues to monitor to ensure ongoing recovery, but as of now we believe the impact has been mitigated. Affected components Overall (Operational) Alerts (Operational) Data Export (Operational)

  4. resolved Sep 12, 2026, 01:37 AM UTC

    Status: Resolved API error rates are now stable. Affected components Alerts (Operational) Data Export (Operational) Overall (Operational)

Read the full incident report →

Minor September 3, 2026

Elevated Error Rates and Delays

Detected by Pingoru
Sep 03, 2026, 11:38 PM UTC
Resolved
Sep 03, 2026, 11:38 PM UTC
Duration
—
Affected: IngestOverallDashboardData ExportAlerts
Timeline · 3 updates
  1. investigating Sep 03, 2026, 09:38 PM UTC

    Status: Investigating We're investigating elevated error rates in our API. Affected components Overall (Partial outage) Alerts (Partial outage) Ingest (Partial outage) Data Export (Degraded performance) Dashboard (Partial outage)

  2. identified Sep 03, 2026, 10:18 PM UTC

    Status: Identified We are experiencing elevated API error rates and data export delays due to a vendor's partial outage. We are working on remediation. Affected components Data Export (Degraded performance) Dashboard (Degraded performance) Overall (Degraded performance) Alerts (Degraded performance) Ingest (Degraded performance)

  3. resolved Sep 03, 2026, 11:38 PM UTC

    Status: Resolved Error rates on the API are back to normal, and data export pipelines have resumed. Affected components Dashboard (Operational) Overall (Operational) Alerts (Operational) Ingest (Operational) Data Export (Operational)

Read the full incident report →

Minor September 2, 2026

Delayed Data Export for Line Items

Detected by Pingoru
Sep 02, 2026, 02:33 PM UTC
Resolved
Sep 02, 2026, 02:33 PM UTC
Duration
—
Affected: Data Export
Timeline · 2 updates
  1. identified Sep 02, 2026, 07:33 AM UTC

    Status: Identified Data export for finalized line items is experiencing delays. All other models (finalized invoices, customers, invoice breakdowns) are not impacted at this time. Affected components Data Export (Degraded performance)

  2. resolved Sep 02, 2026, 02:33 PM UTC

    Status: Resolved Data export for finalized line items has now caught up. The team will continue monitoring. Affected components Data Export (Operational)

Read the full incident report →

Minor September 1, 2026

Elevated latency on arrears invoicing to Stripe

Detected by Pingoru
Sep 01, 2026, 10:17 PM UTC
Resolved
Sep 01, 2026, 10:17 PM UTC
Duration
—
Affected: Dashboard
Timeline · 2 updates
  1. identified Sep 01, 2026, 07:48 PM UTC

    Status: Identified Stripe arrears invoice delivery is experiencing an extended delay for some clients. Impact is isolated to end-of-month usage invoices. Affected components Dashboard (Degraded performance)

  2. resolved Sep 01, 2026, 10:17 PM UTC

    Status: Resolved The bottleneck on arrears invoicing into Stripe has been identified and mitigated. Monitoring shows that Stripe arrears usage invoicing has caught up, resolving the delay. Affected components Dashboard (Operational)

Read the full incident report →

Minor September 1, 2026

Delayed Threshold Billing Processing

Detected by Pingoru
Sep 01, 2026, 01:07 AM UTC
Resolved
Sep 01, 2026, 01:07 AM UTC
Duration
—
Affected: Overall
Timeline · 3 updates
  1. investigating Sep 01, 2026, 01:03 AM UTC

    Status: Investigating We've mitigated an issue that delayed threshold billing purchases. All delayed purchases are now being processed. Affected components Overall (Degraded performance)

  2. monitoring Sep 01, 2026, 01:05 AM UTC

    Status: Monitoring We've mitigated an issue that delayed threshold billing purchases. All delayed purchases are now being processed. Affected components Overall (Degraded performance)

  3. resolved Sep 01, 2026, 01:07 AM UTC

    Status: Resolved All delayed purchases have been processed. Affected components Overall (Operational)

Read the full incident report →

Minor July 28, 2026

Ingest and Alerts are delayed

Detected by Pingoru
Jul 28, 2026, 11:41 AM UTC
Resolved
Jul 28, 2026, 11:41 AM UTC
Duration
—
Timeline · 2 updates
  1. investigating Jul 28, 2026, 10:06 AM UTC

    Status: Investigating We are investigating an increase in aggregation time, which is impacting both the usage pipeline and alert evaluation time. Ingest availability is not impacted. Current delay is roughly 4 mins starting at 07:14UTC.

  2. resolved Jul 28, 2026, 11:41 AM UTC

    Status: Resolved Time to aggregate is back to baseline as of 11:28 UTC and impact to the usage pipeline and alert evaluation has resolved.

Read the full incident report →

Minor July 28, 2026

Delayed Data Export for Draft Invoice and Invoice Breakdowns

Detected by Pingoru
Jul 28, 2026, 04:44 AM UTC
Resolved
Jul 28, 2026, 04:44 AM UTC
Duration
—
Affected: Data Export
Timeline · 2 updates
  1. monitoring Jul 27, 2026, 07:16 PM UTC

    Status: Monitoring Data exports for draft invoices and invoice breakdowns are currently delayed. The pipeline has been mitigated, and backfills are in progress. Contracts, finalized invoices, and other models are not impacted. Affected components Data Export (Partial outage)

  2. resolved Jul 28, 2026, 04:44 AM UTC

    Status: Resolved All backfills are complete, and data export is operational. Affected components Data Export (Operational)

Read the full incident report →

Minor July 22, 2026

API Error Rates Elevated

Detected by Pingoru
Jul 22, 2026, 03:25 AM UTC
Resolved
Jul 22, 2026, 03:25 AM UTC
Duration
—
Affected: IngestOverall
Timeline · 3 updates
  1. investigating Jul 21, 2026, 09:53 PM UTC

    Status: Investigating We are investigating elevated error rates on our API. Ingest is not impacted. Affected components Overall (Partial outage) Ingest (Partial outage)

  2. monitoring Jul 21, 2026, 11:22 PM UTC

    Status: Monitoring API error rates have returned to normal, and the team is continuing to monitor. Affected components Overall (Partial outage) Ingest (Operational)

  3. resolved Jul 22, 2026, 03:25 AM UTC

    Status: Resolved API error rates have resolved. Affected components Overall (Operational) Ingest (Operational)

Read the full incident report →

Minor July 10, 2026

Support Portal Unavailable

Detected by Pingoru
Jul 10, 2026, 10:22 PM UTC
Resolved
Jul 10, 2026, 10:22 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Jul 10, 2026, 05:08 PM UTC

    Status: Investigating Our support portal is currently unavailable. We're investigating a fix.

  2. resolved Jul 10, 2026, 10:22 PM UTC

    Status: Resolved The support portal has been restored.

Read the full incident report →

Minor July 8, 2026

Username/password auth not working

Detected by Pingoru
Jul 08, 2026, 10:58 PM UTC
Resolved
Jul 08, 2026, 10:58 PM UTC
Duration
—
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jul 08, 2026, 10:32 PM UTC

    Status: Investigating We're seeing errors in our web authentication. SAML log-in is currently unaffected. We are investigating Affected components Dashboard (Full outage)

  2. identified Jul 08, 2026, 10:43 PM UTC

    Status: Identified We've identified the issue and are working on resolving ASAP. We are hearing some reports of SAML auth also being down. Affected components Dashboard (Full outage)

  3. monitoring Jul 08, 2026, 10:45 PM UTC

    Status: Monitoring We've deployed a fix and auth is now working. Affected components Dashboard (Operational)

  4. resolved Jul 08, 2026, 10:58 PM UTC

    Status: Resolved This issue has been resolved and mitigations have been put in place. Affected components Dashboard (Operational)

Read the full incident report →

Minor July 8, 2026

Elevated API Errors and Alerts Latency

Detected by Pingoru
Jul 08, 2026, 06:29 PM UTC
Resolved
Jul 08, 2026, 06:29 PM UTC
Duration
—
Affected: OverallAlerts
Timeline · 3 updates
  1. investigating Jul 08, 2026, 05:53 PM UTC

    Status: Investigating Metronome's API and alerts are experiencing elevated error rates and latency. We are investigating. Affected components Alerts (Partial outage) Overall (Partial outage)

  2. monitoring Jul 08, 2026, 06:22 PM UTC

    Status: Monitoring Error rates have recovered. We've identified the issue and have rolled back the issue. We're continuing to monitor Affected components Overall (Operational) Alerts (Operational)

  3. resolved Jul 08, 2026, 06:29 PM UTC

    Status: Resolved We're confident this has been resolved. Affected components Overall (Operational) Alerts (Operational)

Read the full incident report →

Minor July 8, 2026

Elevated API Errors and Latency

Detected by Pingoru
Jul 08, 2026, 01:20 AM UTC
Resolved
Jul 08, 2026, 01:20 AM UTC
Duration
—
Affected: Overall
Timeline · 3 updates
  1. investigating Jul 07, 2026, 10:13 PM UTC

    Status: Investigating Metronome's API is experiencing elevated error rates and latency as of 21:58 UTC. We are investigating. Affected components Overall (Degraded performance)

  2. monitoring Jul 07, 2026, 10:28 PM UTC

    Status: Monitoring API errors have recovered, and we are actively monitoring. Affected components Overall (Operational)

  3. resolved Jul 08, 2026, 01:20 AM UTC

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

Read the full incident report →

Minor July 3, 2026

Some customers missing July draft invoices

Detected by Pingoru
Jul 03, 2026, 01:14 AM UTC
Resolved
Jul 03, 2026, 01:14 AM UTC
Duration
—
Affected: OverallDashboardData ExportAlerts
Timeline · 4 updates
  1. investigating Jul 02, 2026, 02:53 PM UTC

    Status: Investigating We are investing reports of some end customers missing their July draft invoices in the UI and API. We will follow-up with more details as we know more. Affected components Dashboard (Degraded performance) Overall (Degraded performance) Data Export (Degraded performance)

  2. identified Jul 02, 2026, 03:24 PM UTC

    Status: Identified We have identified some end customers are missing their July draft invoice. For these customers, some spend based alerting that depends on the draft invoice will be delayed until the invoice is re-created. These invoices are also not visible via data export, the UI or API. We're working to create these invoices now, and will be reaching out to clients impacted directly with more information. Affected components Dashboard (Degraded performance) Overall (Degraded performance) Alerts (Degraded performance) Data Export (Degraded performance)

  3. monitoring Jul 02, 2026, 03:56 PM UTC

    Status: Monitoring We believe all July draft invoices are now appearing as expected. We are working to confirm this, as well as verify additional impact details. Affected components Alerts (Operational) Data Export (Operational) Dashboard (Operational) Overall (Operational)

  4. resolved Jul 03, 2026, 01:14 AM UTC

    Status: Resolved All systems are working as expected. We are working directly with customers who were impacted to confirm any additional followups or impact. Affected components Dashboard (Operational) Overall (Operational) Alerts (Operational) Data Export (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 →