Fastly will be adding capacity at our Frankfurt (FRA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 14 November 2025 at 21:00 UTC.
Our estimated duration is 2h.
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 completed.
To offer feedback on our status page, click "Give Feedback"
Traffic in Meerut (QAD) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly Engineers detected a performance impacting event affecting the Fastly Compute Services within our Ashburn (IAD) and Chicago (CHI) Points of Presence (POPs).
All other POPs and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Engineering has confirmed that this incident has been fully restored. Customers may have experienced increased latency and errors affecting Fastly Compute Services from Thursday at 23:49 UTC to Friday at 01:12 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-14 01:51:47 UTC
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 adding capacity at our Frankfurt (FRA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 13 November 2025 at 21:00 UTC.
Our estimated duration is 2h.
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 cancelled and will be rescheduled for the 14th of November 2025.
To offer feedback on our status page, click "Give Feedback"
Fastly Engineers detected a performance impacting event affecting the Real-time Analytics services.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We're currently investigating potential impact to performance with our CDN services.
Our engineers are continuing to investigate a performance impact to Europe, Global POP Network (SEV1/0) service.
All other locations and services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Europe, Global POP Network (SEV1/0) 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.
Engineering has confirmed the impact to Europe, Global POP Network (SEV1/0) service has been mitigated.
To provide further clarity on this incident: we initially posted to global components out of an abundance of caution while we investigated. Following further investigation, we can confirm the performance impact was isolated to our Amsterdam (RTM), London (LON), Marseille (MRS), Paris (PAR) and Vienna (VIE) POPs.
We've updated both the status post title and listed components to reflect these findings. This incident remains mitigated.
Engineering has confirmed that London (LON), Marseille (MRS), Vienna (VIE), Paris (PAR), Amsterdam (RTM) POPs has been fully restored. Customers may have experienced elevated errors and/or latency from 17:50 to 18:15 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-12 18:17:01 UTC
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.
Traffic in Vancouver (YVR) has been temporarily rerouted.
All other locations and services are unaffected.
We are investigating elevated errors to our Singapore (SIN) Point of Presence (POP).
All other products and services are unaffected by this incident.
Our engineers believe they have identified the 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.
Engineering has confirmed the impact to Singapore (SIN) POP has been mitigated.
Engineering has confirmed that Singapore (SIN) POP has been fully restored. Customers may have experienced increased latency from 04:50 UTC to 05:30 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-12 05:39:24 UTC
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.
We are investigating elevated errors to our Manila (MNL) 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 Manila (MNL) 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.
Engineering has confirmed the impact to Manila (MNL) POP has been mitigated.
This event has been resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-12 01:00:30 UTC
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.
As part of Fastly’s global network expansion, we will be adding Raipur (RPR), Kochi (QAN) data centers to Fastly's Asia-Pacific (APAC) network.
Traffic served by our Raipur (RPR), Kochi (QAN) data centers will be aggregated into our APAC region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Raipur (RPR), Kochi (QAN) . As such, some customers may see a change in their bills.
Fastly’s standard billing rates are located at https://www.fastly.com/pricing.
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"