- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 26of 100
What to do
Check whether your product depends on Metronome. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 35m it lasted.
Anything that failed between 2026-07-08 17:53 UTC and 2026-07-08 18:29 UTC may need a replay.Subscribe to Metronome's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=metronome works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Metronome 3
- investigating
Metronome's API and alerts are experiencing elevated error rates and latency. We are investigating.
provider
- monitoring
Error rates have recovered. We've identified the issue and have rolled back the issue. We're continuing to monitor
provider
- resolved
We're confident this has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-82f00cbe4c
Is Metronome still down?
No, this incident was resolved 2026-07-08 18:29 UTC. For Metronome's live state, see https://down.guide/metronome.
How long did it last?
35m, from 2026-07-08 17:53 UTC to 2026-07-08 18:29 UTC, by the times Metronome posted.
What caused it?
Metronome hasn't published a root cause. If it does, it shows here.
Where does this come from?
Metronome's official status page, https://status.metronome.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.