- Level
- confirmed
- Worst impact
- Degraded
- Components
- Substack.com
- Down Index
- 20of 100
What to do
Check whether you use Substack Substack.com. 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 55m it lasted.
Anything that failed between 2026-10-09 22:37 UTC and 2026-10-09 23:32 UTC may need a replay.Subscribe to Substack's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=substack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Substack 3
- investigating
Substack is experiencing elevated latencies. We are investigating the issue.
provider
- monitoring
We are seeing recovery and are monitoring the situation.
provider
- resolved
The incident has been 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-bccc57c0c9
Is Substack still down?
No, this incident was resolved 2026-10-09 23:32 UTC. For Substack's live state, see https://down.guide/substack.
How long did it last?
55m, from 2026-10-09 22:37 UTC to 2026-10-09 23:32 UTC, by the times Substack posted.
What was affected?
Substack named Substack.com.
What caused it?
Substack hasn't published a root cause. If it does, it shows here.
Where does this come from?
Substack's official status page, https://substack.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.