Fastly incident
Elevated Errors for Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR)
Fastly experienced a major incident on June 6, 2026 affecting North America and Atlanta (PDK) and 1 more component, lasting 1h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 06, 2026, 01:00 AM UTC
We are investigating elevated errors to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) Points of Presence (POPs) All other products and services are unaffected by this incident.
- investigating Jun 06, 2026, 01:06 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) status page components. 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.
- investigating Jun 06, 2026, 01:53 AM UTC
The fix has been successfully deployed, and we have observed a recovery to only our DFW, DEN, MSP, and EWR POPs. Error rates and latency have returned to nominal levels and we are monitoring stability at these locations. Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our MIA and PDK POPs specifically. All other locations and services are unaffected.
- monitoring Jun 06, 2026, 02:14 AM UTC
Engineering has confirmed the impact to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs) has been mitigated.
- resolved Jun 06, 2026, 02:25 AM UTC
Engineering has confirmed that our our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) POPs have been fully restored. Customers may have experienced increased latency from 00:50 to 01:50 UTC at our DFW, DEN, MSP, and EWR POPs and from 00:50 to 02:13 UTC at our PDK and MIA POPs. 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-06 01:01:14 UTC