- Level
- confirmed
- Worst impact
- Operational
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 35m it lasted.
Anything that failed between 2026-07-28 10:06 UTC and 2026-07-28 11:41 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 2
- investigating
We are investigating an increase in aggregation time, which is impacting both the usage pipeline and alert evaluation time. Ingest availability is not impacted. Current delay is roughly 4 mins starting at 07:14UTC.
provider
- resolved
Time to aggregate is back to baseline as of 11:28 UTC and impact to the usage pipeline and alert evaluation 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-2488c6b4be
Is Metronome still down?
No, this incident was resolved 2026-07-28 11:41 UTC. For Metronome's live state, see https://down.guide/metronome.
How long did it last?
1h 35m, from 2026-07-28 10:06 UTC to 2026-07-28 11:41 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.