Fastly experienced a major incident on June 30, 2026 affecting South America and Buenos Aires (EZE) and 1 more component, lasting 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 30, 2026, 02:31 AM UTC
We're investigating possible performance impact affecting the Buenos Aires (EZE) data center. All other locations and services are unaffected.
- investigating Jun 30, 2026, 02:43 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Buenos Aires (EZE) 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.
- monitoring Jun 30, 2026, 02:50 AM UTC
Engineering has deployed a fix and have confirmed a gradual recovery to Buenos Aires (EZE) POP. We will continue to monitor until we’ve confirmed that customer experience has been fully restored. All other networks and services were unaffected by this incident.
- resolved Jun 30, 2026, 02:53 AM UTC
Engineering has confirmed that Buenos Aires (EZE) POP has been fully restored. Customers may have experienced elevated errors from 02:31 to 02:53 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-06-30 02:43:11 UTC