- Level
- confirmed
- Worst impact
- Degraded
- Components
- Uptime monitoring
- Down Index
- 9of 100
What to do
Check whether you use Instatus Uptime monitoring. 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 0m it lasted.
Anything that failed between 2026-05-21 13:10 UTC and 2026-05-21 13:10 UTC may need a replay.Subscribe to Instatus's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=instatus works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Instatus 1
- resolved
Type: Incident Duration: 10 minutes Affected Components: Uptime monitoring May 21, 13:20:00 GMT+0 - Resolved - We rolled back, so monitors should be working fine now. May 21, 13:10:00 GMT+0 - Identified - We did a faulty release that caused some false monitor alerts to be sent to customers.
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-f612480f0a
Is Instatus still down?
No, this incident was resolved 2026-05-21 13:10 UTC. For Instatus's live state, see https://down.guide/instatus.
How long did it last?
0m, from 2026-05-21 13:10 UTC to 2026-05-21 13:10 UTC, by the times Instatus posted.
What was affected?
Instatus named Uptime monitoring.
What caused it?
Instatus hasn't published a root cause. If it does, it shows here.
Where does this come from?
Instatus's official status page, https://instat.us, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.