Skip to main content
Substack

Substack home page and app home tab errors

Partial outage Lasted 1h 24m · started · Substack's page

Level
confirmed
Worst impact
Partial outage
Components
Substack.com
Down Index
31of 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 1h 24m it lasted.

    Anything that failed between 2025-02-03 19:25 UTC and 2025-02-03 20:49 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 6

  1. investigating

    We are investigating reports of Notes not loading on the Substack homepage.

    provider

  2. investigating

    We have identified an issue causing increased errors from the Substack web destination as well as the home tab of the Substack app. We are working to resolve.

    provider

  3. identified

    We have identified the issue and we're working to resolve the errors from the Substack.com home page and Substack app home tab.

    provider

  4. identified

    We are continuing to work to resolve the increased error rate from the Substack home page and Substack app home tab. Some Substack users may not see Notes in your feed while we work to restore service.

    provider

  5. monitoring

    We have restored the feed for all users on Substack.com and in the Substack app home tab and have seen error rates subside. We are continuing to monitor.

    provider

  6. 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-d30e26da4f

Is Substack still down?

No, this incident was resolved 2025-02-03 20:49 UTC. For Substack's live state, see https://down.guide/substack.

How long did it last?

1h 24m, from 2025-02-03 19:25 UTC to 2025-02-03 20:49 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.