- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Substack. 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 3h 9m it lasted.
Anything that failed between 2026-01-14 17:38 UTC and 2026-01-14 20:47 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 working to investigate the issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This 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-569e57ecb3
Is Substack still down?
No, this incident was resolved 2026-01-14 20:47 UTC. For Substack's live state, see https://down.guide/substack.
How long did it last?
3h 9m, from 2026-01-14 17:38 UTC to 2026-01-14 20:47 UTC, by the times Substack posted.
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.