Resolved after 1 hour 37 minutes, affecting Fanout and Fastly Compute and 1 more, on October 27, 2026.
Engineering has confirmed that Compute, Next-Gen WAF (NGWAF) Services has been fully restored. Customers may have experienced intermittent 5xx errors from 23:05 UTC on October 27 to 00:23 UTC on October 28. Service has been fully restored. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-10-28 00:15:23 UTC
Affected components
Update timeline
- investigating Oct 28, 2026, 12:10 AM UTC
We are investigating elevated errors to our Compute, Next-Gen WAF (NGWAF) Services
- investigating Oct 28, 2026, 12:34 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Compute, Next-Gen WAF (NGWAF) Services. 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.
- monitoring Oct 28, 2026, 12:35 AM UTC
Engineering has confirmed the impact to Compute, Next-Gen WAF (NGWAF) Services has been mitigated.
- resolved Oct 28, 2026, 12:42 AM UTC
Engineering has confirmed that Compute, Next-Gen WAF (NGWAF) Services has been fully restored. Customers may have experienced intermittent 5xx errors from 23:05 UTC on October 27 to 00:23 UTC on October 28. Service has been fully restored. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-10-28 00:15:23 UTC
Your product runs on more than Fastly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services