Substack

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 22:37 UTC

   Substack is experiencing elevated latencies. We are investigating the issue.

2. monitoring 2026-10-09 22:59 UTC

   We are seeing recovery and are monitoring the situation.

3. resolved 2026-10-09 23:32 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-30 15:17 UTC

   Posts and notes are sending, but delivery stats are experiencing delays.

2. identified 2026-08-30 15:59 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-30 17:22 UTC

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

4. resolved 2026-08-30 18:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-18 04:23 UTC

   We are currently investigating this issue.

2. resolved 2026-08-18 04:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-16 10:06 UTC

   We're aware of an issue affecting how some media loads on Substack (particularly images).

2. monitoring 2026-07-16 11:22 UTC

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

3. resolved 2026-07-16 16:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-03 13:58 UTC

   We are experiencing delays in post email delivery due to an outage from a third party service provider.

2. monitoring 2026-06-03 14:16 UTC

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

3. resolved 2026-06-03 14:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Email delivery, Subscription invoice processing, Substack.com, Push Notifications, Custom domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 19:12 UTC

   We are experiencing an issue with a provider.

2. identified 2026-04-22 19:36 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-22 19:45 UTC

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

4. resolved 2026-04-22 20:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-27 22:20 UTC

   We’re investigating an issue affecting reported open rates for some publishers. Current evidence suggests this is related to how Gmail loads tracking pixels, and does not indicate a change in engagement or deliverability. We take responsibility for ensuring these metrics are...

2. resolved 2026-05-11 17:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-27 00:41 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2026-02-27 03:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-26 23:10 UTC

   We're aware of an issue affecting loading publisher stats

2. identified 2026-02-26 23:40 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-02-26 23:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-12 23:25 UTC

   We are currently investigating this issue.

2. identified 2026-02-12 23:42 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-02-12 23:43 UTC

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

4. resolved 2026-02-13 00:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-11 14:24 UTC

   We are investigating an issue loading substack.com

2. identified 2026-02-11 14:41 UTC

   We've identified the issue and are deploying changes to address.

3. identified 2026-02-11 14:53 UTC

   We are continuing to work to restore service. Currently all Substack clients and services are experiencing elevated error rates and degraded performance.

4. identified 2026-02-11 14:57 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-02-11 15:10 UTC

   We have deployed a fix and are continuing to see recovery.

6. monitoring 2026-02-11 15:15 UTC

   All Substack services have been restored and error rates and latency have returned to normal levels. Our team is continuing to monitor.

7. resolved 2026-02-11 15:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-15 12:35 UTC

   We're currently investigating an issue affecting load times of notes and inboxes

2. monitoring 2026-01-15 12:47 UTC

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

3. resolved 2026-01-15 12:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-14 17:38 UTC

   Substack is experiencing elevated latencies. We are working to investigate the issue.

2. monitoring 2026-01-14 19:25 UTC

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

3. resolved 2026-01-14 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-05 17:17 UTC

   We're experiencing a delay in processing the automated read-alouds for posts in the apps.

2. resolved 2026-01-06 05:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-22 23:31 UTC

   We are currently observing increased latency on Substack surfaces and are investigating the issue.

2. monitoring 2025-12-22 23:52 UTC

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

3. resolved 2025-12-23 00:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com, Custom domains

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 14:39 UTC

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

2. monitoring 2025-11-18 14:45 UTC

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

3. resolved 2025-11-18 15:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Push Notifications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-05 16:52 UTC

   We are experiencing delays due to a service provider outage.

2. monitoring 2025-11-05 17:29 UTC

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

3. resolved 2025-11-05 17:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 13:41 UTC

   We are experiencing delays with processing scheduled posts related to an outage from one of our service providers. Our team is investigating.

2. investigating 2025-10-20 13:49 UTC

   We are also seeing issues with publication dashboards including partial outages across the subscriber tab and some statistics. We are working to mitigate.

3. identified 2025-10-20 14:12 UTC

   We are seeing recovery of our publisher dashboard functionality. Other service functions such as scheduled posts continue to be degraded.

4. identified 2025-10-20 16:51 UTC

   We continue to experience delays with processing scheduled posts related to an outage from one of our service providers. Users can publish posts manually to bypass this. Our team is still investigating.

5. monitoring 2025-10-20 21:50 UTC

   Scheduled post sends are operational and we have caught up with the backlog.

6. resolved 2025-10-21 00:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery, Push Notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-04 16:06 UTC

   We are experiencing delays in sending out email and push notifications for published posts.

2. identified 2025-10-04 16:25 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-10-04 19:22 UTC

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

4. resolved 2025-10-04 20:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-20 14:42 UTC

   We are currently investigating this issue.

2. monitoring 2025-09-20 16:08 UTC

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

3. resolved 2025-09-20 16:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Email delivery, Substack.com, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-15 15:24 UTC

   We are currently investigating reports of increased latency and slow response times across Substack.

2. investigating 2025-09-15 15:34 UTC

   We are continuing to investigate increased latency and error rates across Substack.

3. identified 2025-09-15 15:42 UTC

   We have identified an issue and are seeing normal performance across all systems.

4. identified 2025-09-15 15:50 UTC

   We are continuing to investigate increased latency and error rates across Substack.

5. identified 2025-09-15 16:38 UTC

   We are working to resolve the remaining performance issues across Substack and expect to see recovery shortly.

6. monitoring 2025-09-15 16:46 UTC

   We are seeing recovery of performance across Substack and are monitoring the issue.

7. monitoring 2025-09-15 16:53 UTC

   As part of the earlier incident, we are noting delays in analytics updating and post email delivery. We are working to resolve the issue.

8. identified 2025-09-15 17:43 UTC

   We are seeing recurrence of increased error rates and degraded performance across Substack.

9. monitoring 2025-09-15 18:39 UTC

   Substack is operating normally and our team is monitoring.

10. resolved 2025-09-15 19:12 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-30 16:17 UTC

   We are investigating a delay in the sending of scheduled posts.

2. monitoring 2025-08-30 16:30 UTC

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

3. resolved 2025-08-30 16:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-26 14:06 UTC

   We are experiencing an issue with a service provider that is causing livestream creation to be broken.

2. resolved 2025-08-26 14:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-11 16:15 UTC

   We are currently investigating this issue.

2. monitoring 2025-08-11 16:27 UTC

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

3. resolved 2025-08-11 16:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Email delivery, Subscription invoice processing, Substack.com, Push Notifications, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-23 17:45 UTC

   We are currently investigating a higher error rate when trying to load Substack

2. identified 2025-06-23 17:51 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-06-23 18:04 UTC

   Restored functionality on Substack.com and app. We are continuing to work on a fix for some delays in email delivery.

4. monitoring 2025-06-23 18:14 UTC

   Continuing to bring systems back online. Writer dashboard stats including open rates may be delayed or temporarily inaccurate.

5. resolved 2025-06-24 05:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-23 16:50 UTC

   We are currently investigating a higher error rate when trying to load Substack

2. identified 2025-06-23 16:56 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-06-23 16:57 UTC

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

4. resolved 2025-06-23 17:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards, Email delivery, Push Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-24 14:47 UTC

   We are currently investigating this issue.

2. monitoring 2025-05-24 15:20 UTC

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

3. resolved 2025-05-25 03:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-30 13:31 UTC

   We are experiencing a delay in reader activity statistics relating to email deliveries/opens. Emails continue to send as normal, though their stats are currently delayed.

2. identified 2025-04-30 14:21 UTC

   We have identified the issue related to delayed statistics for email deliveries and opens. We are currently processing enqueued events and working toward full recovery.

3. identified 2025-05-01 04:15 UTC

   Our engineers are backfilling missing data from the impacted time period. We'll continue to update the incident as that process completes.

4. identified 2025-05-01 23:47 UTC

   At this time, email delivery statistics are accurate, but we're still in the process of backfilling email open statistics between Tuesday and Wednesday afternoon.

5. resolved 2025-05-02 01:21 UTC

   All email analytics should be up to date.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Email delivery, Subscription invoice processing, Substack.com, Push Notifications, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-29 17:03 UTC

   We are currently investigating this issue.

2. investigating 2025-04-29 17:49 UTC

   This issue is causing performance degradation across the system.

3. investigating 2025-04-29 17:52 UTC

   The website is down.

4. identified 2025-04-29 18:03 UTC

   We are experiencing elevated error rates across all Substack applications including publication websites, Substack.com, and the Substack apps. We have identified the issue and we are working toward recovery.

5. identified 2025-04-29 18:11 UTC

   We are beginning to see recovery across Substack and error rates are returning the normal levels.

6. identified 2025-04-29 18:15 UTC

   We are continuing to see recovery. Substack publications, the publisher dashboard, and other functionality are fully recovered. We continue to work on increased error rates across Substack.com, the Substack app, and the post editor.

7. monitoring 2025-04-29 18:41 UTC

   We are seeing full recovery across Substack and our team is now monitoring.

8. resolved 2025-04-29 19:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-03-24 23:41 UTC

   We have identified an issue preventing users from loading the notes feed and are implementing a fix

2. monitoring 2025-03-25 00:02 UTC

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

3. resolved 2025-03-25 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-11 16:43 UTC

   We are investigating reports of delayed email delivery for posts published on Substack.

2. identified 2025-03-11 16:52 UTC

   We have identified the cause of the email delays and are working to resolve.

3. monitoring 2025-03-11 16:57 UTC

   The issue causing delays to email delivery on posts has been addressed.

4. resolved 2025-03-11 17:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-01 15:38 UTC

   We are currently investigating an issue causing problems loading the Notes feed.

2. monitoring 2025-03-01 15:46 UTC

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

3. resolved 2025-03-01 22:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-28 23:43 UTC

   Publisher Dashboard and Notifications are experiencing slowdowns. We are investigating the cause.

2. identified 2025-02-28 23:45 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-02-28 23:56 UTC

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

4. resolved 2025-03-01 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-03 19:25 UTC

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

2. investigating 2025-02-03 19:29 UTC

   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.

3. identified 2025-02-03 19:37 UTC

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

4. identified 2025-02-03 20:14 UTC

   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.

5. monitoring 2025-02-03 20:31 UTC

   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.

6. resolved 2025-02-03 20:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-01-27 21:08 UTC

   We're experiencing a delay in processing some stats across the platform. Data on various dashboards may be out of date.

2. monitoring 2025-01-27 21:57 UTC

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

3. resolved 2025-01-27 22:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-21 23:44 UTC

   We are investigating reports of increased latency and errors for Substack.com, publication websites, and the Substack app.

2. investigating 2025-01-21 23:48 UTC

   We are continuing to investigate reports of increased latency and errors for all Substack websites and applications.

3. identified 2025-01-22 00:12 UTC

   We have identified the issue and are beginning to see recovery across all Substack websites and applications.

4. monitoring 2025-01-22 00:20 UTC

   Substack websites and applications are fully operational and our team is monitoring.

5. resolved 2025-01-22 00:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-10 15:13 UTC

   We are currently investigating this issue.

2. monitoring 2025-01-10 15:33 UTC

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

3. resolved 2025-01-10 18:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-19 13:13 UTC

   We are currently investigating this issue.

2. monitoring 2024-12-19 13:44 UTC

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

3. resolved 2024-12-19 13:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Email delivery, Subscription invoice processing, Substack.com, Push Notifications, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-12-13 16:21 UTC

   We are experiencing an outage, but we are recovering.

2. identified 2024-12-13 16:25 UTC

   We are currently experiencing an elevated error rate to Substack web sites and through our mobile application, but are seeing recovery. We are continuing to work toward mitigation.

3. monitoring 2024-12-13 16:28 UTC

   Substack services are fully available. We are continuing to monitor.

4. resolved 2024-12-13 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-29 22:27 UTC

   We are currently investigating this issue.

2. identified 2024-10-29 22:29 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-10-29 22:45 UTC

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

4. resolved 2024-10-29 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-23 02:21 UTC

   We are currently investigating this issue.

2. identified 2024-10-23 02:39 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2024-10-23 02:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Subscription invoice processing, Substack.com, Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-10-10 19:40 UTC

   We are currently investigating an issue related to managing subscriptions.

2. resolved 2024-10-10 20:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-10-04 13:40 UTC

   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.

2. monitoring 2024-10-04 19:14 UTC

   We have resolved this issue and are monitoring.

3. resolved 2024-10-04 23:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Email delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-01 14:04 UTC

   We are investigating reports that some posts are not being delivered via email.

2. identified 2024-10-01 14:08 UTC

   We can confirm delays in email deliveries for Substack posts starting at 9am EDT. We are working to resolve the issues.

3. identified 2024-10-01 14:24 UTC

   We are continuing to work on addressing delays in email deliveries.

4. monitoring 2024-10-01 14:32 UTC

   The delays in post delivery have been resolved and previously scheduled posts are currently being delivered. We are monitoring our systems to ensure delivery.

5. resolved 2024-10-01 15:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-18 21:19 UTC

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

2. resolved 2024-09-18 21:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Custom domains

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-15 19:44 UTC

   We've identified an issue preventing the setup of new custom domains and are working to restore functionality.

2. resolved 2024-09-15 21:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-23 17:36 UTC

   We are investigating reports of increased errors and Latency from all Substack services.

2. investigating 2024-08-23 17:50 UTC

   We have identified the cause of the issue and are working toward resolution. At this time Substack is experiencing degraded performance across the web and Substack app. We are working to resolve as soon as possible.

3. identified 2024-08-23 18:05 UTC

   We are continuing to work toward resolution. At this time Substack is experiencing degraded performance across the web and Substack app. We are working to resolve as soon as possible.

4. identified 2024-08-23 18:29 UTC

   We are continuing to work toward resolution and anticipate recovery starting shortly. At this time Substack is experiencing degraded performance across the web and Substack app. We are working to resolve as soon as possible.

5. identified 2024-08-23 18:35 UTC

   We are beginning to see recovery across Substack. We are continuing to work toward full resolution.

6. monitoring 2024-08-23 18:37 UTC

   Substack is operating normally. We are continuing to monitor.

7. resolved 2024-08-23 19:06 UTC

   This incident has been resolved and Substack is operating normally.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Substack publications, Writer dashboards, Substack.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-13 19:24 UTC

   We are investigating reports of increased error rates across Substack.

2. identified 2024-08-13 19:27 UTC

   We have resolved the issue and have fully recovered. We will continue to monitor.

3. monitoring 2024-08-13 19:29 UTC

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

4. resolved 2024-08-13 19:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Push Notifications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-08-04 19:08 UTC

   We've identified an issue with delays in push notifications due to an outage at our push notification delivery provider, OneSignal. We expect all notifications to be delivered as normal once the issue is resolved.

2. resolved 2024-08-04 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.

Affected: Writer dashboards

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2024-07-30 22:55 UTC

   We've investigated an issue with delays in publisher stats due to an outage at our data processing provider, Amazon Web Services. We expect no data to be lost and stats to appear as normal once the issue is resolved.

2. monitoring 2024-07-31 03:15 UTC

   We're continuing to monitor an issue with delays in publisher stats due to an outage at our data processing provider, Amazon Web Services. We expect no data to be lost and stats to appear as normal once the issue is resolved, which we expect will be by 11 PM PT at the latest.

3. monitoring 2024-07-31 04:53 UTC

   The outage at Amazon Web Services has been resolved and we're processing the delayed data. We expect stats to be fully up to date by 11:30 PM PT.

4. resolved 2024-07-31 07:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Substack's status page.