Metronome incident

Re-enabling previously unsuccessful threshold billing configurations degraded

Minor Resolved View vendor source →

Metronome experienced a minor incident on March 14, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 14, 2026, 04:01 AM UTC
Resolved
Mar 14, 2026, 04:01 AM UTC
Duration
—
Detected by Pingoru
Mar 14, 2026, 04:01 AM UTC

Update timeline

  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.