Impacted performance to our Content Delivery (CDN)
Impacted performance to our Content Delivery (CDN)
19 August 2026, 12:15 UTC
19 August 2026, 12:15 UTC
We are investigating a small number of requests receiving an empty response body where content is expected. Impact is limited to requests that use Streaming Miss and are eligible for HTTP response revalidation.
All other products and services are unaffected by this incident.
20 August 2026, 23:32 UTC
20 August 2026, 23:32 UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Content Delivery (CDN) status page component.
We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.
All other products and services are unaffected by this incident.
21 August 2026, 00:33 UTC
21 August 2026, 00:33 UTC
Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our Content Delivery (CDN) service.
All other locations and services are unaffected.
21 August 2026, 10:19 UTC
21 August 2026, 10:19 UTC
Engineering has confirmed the impact to our Content Delivery (CDN) service has been mitigated.
22 August 2026, 03:15 UTC
22 August 2026, 03:15 UTC
Fastly Engineering continues to monitor for any unexpected ongoing impact.
If your users see empty response bodies after 17:00 PM UTC on August 21, 2026 on services using the streaming miss feature, please contact Fastly Support.
26 August 2026, 23:39 UTC
26 August 2026, 23:39 UTC
Engineering has confirmed that our Content Delivery (CDN) has been fully restored.
Customers may have experienced empty response body where content is expected for requests that used Streaming Miss and were eligible for HTTP response revalidation from 12:15 on August 19 to 00:51 on August 24 UTC.
This incident is resolved.
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.