Skip to main content
Menu
Substack

Incident

Mobile App Issues

Operational Lasted 13m · started · Substack's page

DWN-97fae0c626

Level
confirmed
Worst impact
Operational
Components
Substack.com

What to do

  • Check whether you use Substack Substack.com. 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 13m it lasted.

    Anything that failed between 2024-09-18 21:19 UTC and 2024-09-18 21: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 2

  1. identified

    We're working on remedying an issue causing many parts of the Substack iOS and Android apps to not load properly.

    provider

  2. 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-97fae0c626

Is Substack still down?

No, this incident was resolved 2024-09-18 21:32 UTC. For Substack's live state, see https://down.guide/providers/substack.

How long did it last?

13m, from 2024-09-18 21:19 UTC to 2024-09-18 21: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.