- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on Mercury. 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 38m it lasted.
Anything that failed between 2026-09-01 17:57 UTC and 2026-09-01 18:36 UTC may need a replay.Subscribe to Mercury's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mercury works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mercury 2
- investigating
We’re investigating reports of intermittent issues affecting inbound and outbound calls with our Support team that may be impacting some customers. We are aware of this issue and our team is actively looking into it. We'll share an update as soon as we have more information. No action is needed from you at this time.
provider
- resolved
This incident has been resolved. Phone calls with our Support team are fully restored and operating normally. No further action is needed. Thank you for your patience.
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-a22bcd2a8b
Is Mercury still down?
No, this incident was resolved 2026-09-01 18:36 UTC. For Mercury's live state, see https://down.guide/mercury.
How long did it last?
38m, from 2026-09-01 17:57 UTC to 2026-09-01 18:36 UTC, by the times Mercury posted.
What caused it?
Mercury hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mercury's official status page, https://status.mercury.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.