Issues loading Notes
Timeline · 2 updates
- investigating Aug 18, 2026, 04:23 AM UTC
We are currently investigating this issue.
- resolved Aug 18, 2026, 04:54 AM UTC
This incident has been resolved.
Substack had 18 outages in the last 2 years totaling 1127h 55m of downtime — averaging 0.7 incidents per month.
There were 18 Substack outages since August 26, 2025 totaling 1127h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
We're aware of an issue affecting how some media loads on Substack (particularly images).
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing delays in post email delivery due to an outage from a third party service provider.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing an issue with a provider.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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 accurate and are prioritizing improvements to our open rate tracking so this is resolved as quickly as possible. We will continue to provide updates here as we learn more.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're aware of an issue affecting loading publisher stats
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Substack is experiencing elevated latencies. We are working to investigate the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing a delay in processing the automated read-alouds for posts in the apps.
This incident has been resolved.
We are currently observing increased latency on Substack surfaces and are investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing delays due to a service provider outage.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing delays with processing scheduled posts related to an outage from one of our service providers. Our team is investigating.
We are also seeing issues with publication dashboards including partial outages across the subscriber tab and some statistics. We are working to mitigate.
We are seeing recovery of our publisher dashboard functionality. Other service functions such as scheduled posts continue to be degraded.
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.
Scheduled post sends are operational and we have caught up with the backlog.
This incident has been resolved.
We are experiencing delays in sending out email and push notifications for published posts.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating a delay in the sending of scheduled posts.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing an issue with a service provider that is causing livestream creation to be broken.
This incident has been resolved.