Fastly experienced a major incident on July 2, 2026 affecting North America and Palo Alto (PAO) and 1 more component, lasting 1h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 02, 2026, 06:34 PM UTC
We are investigating elevated errors with Compute at our Palo Alto (PAO) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Jul 02, 2026, 07:16 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting our Palo Alto (PAO) POP. 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 Jul 02, 2026, 07:28 PM UTC
Engineering has confirmed the impact to our Palo Alto (PAO) POP has been mitigated.
- resolved Jul 02, 2026, 07:38 PM UTC
Engineering has confirmed that our Palo Alto (PAO) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 18:34 to 19:12 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. Status Post, Created Date/Time: 2026-07-02 18:53:40 UTC