- Level
- confirmed
- Worst impact
- Degraded
- Components
- Incident response, Private status pages, Maintenance Automations
- Down Index
- 11of 100
What to do
Check whether you use Instatus Incident response, Private status pages, Maintenance Automations. 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 2025-10-20 07:35 UTC and 2025-10-20 07:35 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: 2 hours Affected Components: Incident response, Private status pages, Maintenance Automations Oct 20, 09:35:00 GMT+0 - Resolved - This incident has been resolved. Oct 20, 07:35:00 GMT+0 - Identified - We faced issues with some of our services, including scheduled maintenance periods, private status pages, and adding incidents for some customes. This was caused by outages to our providers including AWS and Vercel.
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-8de0e72a4d
Is Instatus still down?
No, this incident was resolved 2025-10-20 07:35 UTC. For Instatus's live state, see https://down.guide/instatus.
How long did it last?
0m, from 2025-10-20 07:35 UTC to 2025-10-20 07:35 UTC, by the times Instatus posted.
What was affected?
Instatus named Incident response, Private status pages, Maintenance Automations.
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.