North America
We're investigating possible performance impact affecting the North America data centers.
All other locations and services are unaffected.
Our engineers have identified the contributing factor causing the issue impacting our services in North America.
Mitigation actions are in progress, and we are seeing early signs of improvement. We will post a new update once recovery is confirmed.
All other products and services remain unaffected by this incident.
Engineering has deployed a fix and have confirmed a gradual recovery to North America POPs. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.
All other networks and services were unaffected by this incident.
Engineering has confirmed that North America POPs have been fully restored. Customers may have experienced elevated errors and latency from 1:50 to 3:34 UTC.
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.
Fastly will be performing scheduled maintenance on our New York (TSS) data center from 17 November 2026, 05:00 UTC - 17 November 2026, 06:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
Fastly Engineers detected a performance impacting event affecting the Dallas (DFW) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Between 00:21 UTC and 00:24 UTC on November 4, 2026, we experienced a performance impact to the Auckland (AKL), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Chicago (CHI), Columbus (CMH), Dallas (DFW), Denver (DEN), Detroit (DTW) , Dubai (DXB), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Newark (EWR), Palo Alto (PAO), Portland (PDX), San Jose (SJC), Seattle (BFI), Toronto (YYZ), New York (NYC), Los Angeles (LAX), Los Angeles (HHR), Jacksonville (JAX) Point of Presence (POPs).
During this time, customers may have experienced elevated errors and latency.
The issue has been resolved, and all services are operating normally. No other POPs or services were affected.
Traffic in Kansas City (MCI) has been temporarily rerouted.
All other locations and services are unaffected.
We are investigating elevated errors to our McAllen (MFE) Point of Presence (POP).
All other products and services are unaffected by this incident.
Our engineers believe they have identified contributing factor causing the issue impacting the McAllen (MFE) 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.
Engineering has confirmed the impact to McAllen (MFE) POP has been mitigated.
This event has been resolved.
Traffic in New York (TSS) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly will be performing scheduled maintenance on our New York (TSS) data center from 23 October 2026, 04:00 UTC - 23 October 2026, 10:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
Fastly will be adding capacity at our Toronto (YYZ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 15 October 2026 at 04:00 UTC.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses ( https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges ). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com .
The scheduled maintenance has been extended to 16 October 2026 at 18:00 UTC. We will provide updates as necessary.
Fastly will be adding capacity at our Miami (MIA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 30 September 2026 at 06:00 UTC.
Our estimated duration is 4h.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.