Fastly
Last updated: 8/6/2026, 12:03:44 PM
Active Incidents
Possible Errors for API & Configuration Management
We are investigating an issue causing elevated 503 errors and slowness affecting api.fastly.com and manage.fastly.com. Our engineers are actively working to diagnose the contributing factor.
We will provide another update as more information becomes available.
Port Blair (IXZ) Rerouted Traffic
Traffic in Port Blair (IXZ) has been temporarily rerouted.
All other locations and services are unaffected.
Data Center Capacity Expansion for Toronto (YYZ)
This maintenance has been cancelled and will be rescheduled at a later date.
St. Louis (STL) Rerouted Traffic
Traffic in St. Louis (STL) has been temporarily rerouted.
All other locations and services are unaffected.
Data Center Capacity Expansion for Toronto (YYZ)
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 21 July 2026 at 03:00 UTC.
Our estimated duration is 1d.
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.
Srinagar-Nahota (QBG) Rerouted Traffic
Traffic in Srinagar-Nahota (QBG) has been temporarily rerouted.
All other locations and services are unaffected.
Image Optimizer Performance Issues
Our engineers believe they have identified the contributing factor causing the issue impacting our Image Optimization service.
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.
Image Optimizer Performance Issues
We're currently investigating performance issues with our Image Optimization service in Europe.
All other services are unaffected.
Elevated Latency for Singapore (SIN)
Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (SIN) 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.
Elevated Latency for Singapore (SIN)
We are investigating an issue causing elevated latency (high Time To First Byte (TTFB)) for our Singapore (SIN) Point of Presence (POP).
Our engineers have taken steps to reduce the impact and are observing improvement while they continue to investigate the contributing factor.
We will provide another update as more information becomes available or within the next hour.
All other products and services are unaffected by this incident.
Data Center Capacity Expansion for Sao Paulo (GRU)
Fastly will be adding capacity at our Sao Paulo (GRU) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 11 July 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). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.
Possible errors in our Kolkata (CCU) POP
Our engineers believe they have identified contributing factor causing the issue impacting the Kolkata (CCU) 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.
Possible errors in our Kolkata (CCU) POP
We are investigating reports of intermittent latency and errors impacting customers served through the Kolkata (CCU) Point of Presence.
Traffic has been rerouted to nearby regions while our engineers investigate. Customers may experience intermittent impact during this time as traffic stabilizes on alternate paths.
Our ability to deliver network services on all other locations, and our ability to security services are not affected by this incident. We will provide another update as more information becomes available.
Possible errors in our Kolkata (CCU) POP
Traffic in Kolkata (CCU) has been temporarily rerouted.
All other locations and services are unaffected.
Recently Resolved Incidents
Possible Errors for API & Configuration Management
Engineering has confirmed that api.fastly.com and manage.fastly.com have been fully restored.
Customers may have experienced possible errors, including elevated 503 responses and slow or failed access, from 06:03 to 07:37 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.
Possible Errors for API & Configuration Management
We have observed a recovery of our API and configuration management services (api.fastly.com and manage.fastly.com).
Error rates and response times have returned to nominal levels.
Our engineers are continuing to monitor the platform closely to ensure stability before we resolve this incident.
All other products and services are unaffected by this incident.
LA - Santa Clara (RHV) Rerouted Traffic
This event has been resolved.
LA - Santa Clara (RHV) Rerouted Traffic
Traffic remains rerouted away from our Santa Clara (RHV) Point of Presence (POP) while our engineers continue to work on mitigation. Customers may experience slightly elevated latency while traffic is served from neighboring POPs.
This POP will remain offline until further notice. We will provide another update once traffic has been restored to this location.
All other products and services are operating normally.
LA - Santa Clara (RHV) Rerouted Traffic
We are investigating an issue causing connection failures and elevated errors for some customers connecting through our Santa Clara (RHV) Point of Presence (POP).
We have rerouted traffic away from this location while our engineers work on mitigation. Customers may experience slightly elevated latency while traffic is served from neighboring POPs.
All other products and services are operating normally.
Engineering has confirmed that our API & Configuration Management services has been fully restored. Customers may have experienced delayed or failed Varnish Configuration Language (VCL) deployments and API failures on https://manage.fastly.com/ from 17:49 to 18:09 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.
Fastly Engineers detected a performance impacting event affecting our API & Configuration Management.
All data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Srinagar-Nahota (QBG) Rerouted Traffic
This event has been resolved.
St. Louis (STL) Rerouted Traffic
This event has been resolved.
Image Optimizer Performance Issues
Image Optimization service has been fully restored and is operating normally in all regions.
Our engineers identified and resolved the contributing factor. Services are no longer experiencing elevated latency or request queuing.
Impact window: July 17, 2026 at 19:45 UTC through July 18, 2026 at 12:27 UTC (approximately 16 hours 42 minutes).
We apologize for any disruption this may have caused. If you continue to experience issues, please contact our support team.
Showing 10 of 17 resolved incidents
Scheduled Maintenance
Planned Maintenance for Alerts
We will be performing maintenance on our Fastly Alerts and its applicable API endpoint on August 7, 2026 from 19:00 to 20:00 UTC (~1 hour).
What’s next? What do I have to do?
Nothing. All actions taken during this planned maintenance belong to Fastly. Customers may experience a disruption lasting up to 1 minute when attempting to access Fastly Alerts and its API endpoint during this maintenance period.
Customers with any questions or concerns may engage with our Support team through https://support.fastly.com.
API Discovery Dashboard Maintenance
Fastly will be performing maintenance on our API Discovery Dashboard on August 3, 2026 from 18:00 to 19:00 UTC (~ 60 minutes duration).
During this planned event, there will be a 5-minute window where data displayed in the API Discovery Dashboard will be stale. We are still capturing API data during the maintenance window, but new data won't be visible until maintenance is complete.
No data will be lost from this maintenance.
If you have any questions about this status post, please reach out to your technical account management team or contact Fastly Support directly.
API Discovery Dashboard Maintenance
The scheduled maintenance has been completed.
Data Center Capacity Expansion for Sao Paulo (GRU)
The scheduled maintenance has been completed.