Skip to main content
Substack

Posts incorrectly auto paywalled

Degraded Lasted 9h 25m · started · Substack's page

Level
confirmed
Worst impact
Degraded
Components
Substack publications
Down Index
25of 100

What to do

  • Check whether you use Substack Substack publications. 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 9h 25m it lasted.

    Anything that failed between 2024-10-04 13:40 UTC and 2024-10-04 23:05 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

  1. identified

    We have identified a bug where some posts where automatically paywalled incorrectly. We are currently working to correct this and will provide updates here shortly.

    provider

  2. monitoring

    We have resolved this issue and are monitoring.

    provider

  3. 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-56f660b5e1

Is Substack still down?

No, this incident was resolved 2024-10-04 23:05 UTC. For Substack's live state, see https://down.guide/substack.

How long did it last?

9h 25m, from 2024-10-04 13:40 UTC to 2024-10-04 23:05 UTC, by the times Substack posted.

What was affected?

Substack named Substack publications.

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.