- Level
- confirmed
- Worst impact
- Degraded
- Components
- Custom domains
- Down Index
- 22of 100
What to do
Check whether you use Substack Custom domains. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 53m it lasted.
Anything that failed between 2024-09-15 19:44 UTC and 2024-09-15 21:37 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 2
- identified
We've identified an issue preventing the setup of new custom domains and are working to restore functionality.
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-9a518b9b9d
Is Substack still down?
No, this incident was resolved 2024-09-15 21:37 UTC. For Substack's live state, see https://down.guide/providers/substack.
How long did it last?
1h 53m, from 2024-09-15 19:44 UTC to 2024-09-15 21:37 UTC, by the times Substack posted.
What was affected?
Substack named Custom domains.
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.