Metronome incident
Re-enabling previously unsuccessful threshold billing configurations degraded
Update timeline
- 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.
- 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.
- 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.
Looking to track Metronome downtime and outages?
Pingoru polls Metronome's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Metronome reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Metronome alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required