Rewindex

CompaniesSubstackIncidents

Substack: Substack is experiencing issues

MinorStatus: resolvedStarted Resolved (38 min)3 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Substack’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +3 h 9 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Substack (this incident)posted +3 h 9 min
same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Substack (this incident)posted +3 h 9 min
Substack is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Substack (this incident)<br/>posted +3 h 9 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Writer dashboardsSubstack publicationsSubstack.comCustom domains

Timeline of updates

  1. investigating

    We are experiencing issues caused by a service provider, some access to Substack might be limited

  2. monitoring

    A fix has been implemented and we are monitoring the results.

  3. resolved

    This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Substack profileRecent Substack incidentsMarkdownJSON