- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 1h 42m it lasted.
Anything that failed between 2026-05-27 20:29 UTC and 2026-05-27 22:12 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 4
- investigating
Metronome's API is experiencing elevated error rates and latency due to a database infrastructure issue. We have identified the underlying cause and are working to restore full performance.
provider
- investigating
We have applied a mitigation and API performance has begun to recover. Some users may continue to experience intermittent issues while we monitor for full recovery.
provider
- monitoring
We've identified the root cause and have made a fix. Latency should be resolving now. We're continuing to monitor.
provider
- resolved
Performance has remained stable and this situation has 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-dcb8b536f0
Is Metronome still down?
No, this incident was resolved 2026-05-27 22:12 UTC. For Metronome's live state, see https://down.guide/metronome.
How long did it last?
1h 42m, from 2026-05-27 20:29 UTC to 2026-05-27 22:12 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.