Infrastructure & CDN
Fastly will be adding capacity at our Fortaleza (FOR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 April 2026 at 04: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). Custome...
Fastly will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 16 April 2026 at 23: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 ...
Engineering has confirmed that Hong Kong (HKG) POP has been fully restored. Customers may have experienced slow loading and elevated errors from 1:57am to 2:17am 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 i...
Our engineers believe they have identified contributing factor causing the issue impacting Hong Kong (HKG) POP. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
This event has been resolved.
Traffic in Minneapolis (STP) has been temporarily rerouted. All other locations and services are unaffected.
This event has been resolved.
Traffic in Houston (IAH) has been temporarily rerouted. All other locations and services are unaffected.
During this incident, customers may have experienced issues with our API services from 10:36 to 11:00 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Fastly Engineers detected a performance impacting event affecting our API Services. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
This event has been resolved.
Our engineers believe they have identified contributing factor causing the issue impacting the Port Blair (IXZ) 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.
We are investigating elevated errors to our Port Blair (IXZ) Point of Presence (POP) All other products and services are unaffected by this incident.
This event has been resolved.
Traffic in Hong Kong (HKG) has been temporarily rerouted. All other locations and services are unaffected.
This event has been resolved.
Fastly Engineers detected a performance impacting event affecting the Wellington (WLG) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
This incident has been resolved.
Fastly Engineers detected a performance impacting event affecting the API Services, Image Optimization , Terraform and use of those services via the Fastly app. Between 20:37 UTC and 21:15 UTC on April 7, 2026, customers attempting to disable Service Level products or enable/disable Image Optimizer via the API may have experienced errors, with affected requests returning 500 responses. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performa...
During this incident, customers may have experienced elevated errors and timeouts from 19:02 to 19:10 UTC (approximately 8 minutes). This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.