Metronome incident
Re-enabling previously unsuccessful threshold billing configurations degraded
Resolved after 2 days 4 hours, on March 11, 2026.
We have identified all affected customers from this incident. If you have been impacted, a Metronome representative will reach out.
Update timeline
- 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.
- 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.
- 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.
Your product runs on more than Metronome
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services