As part of Fastly’s global network expansion, we will be adding Brasilia (BSB) data center to Fastly's South America network.
Traffic served by our Brasilia (BSB) data center will be aggregated into our South America region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Brasilia (BSB) . As such, some customers may see a change in their bills.
Fastly’s standard billing rates are located at https://www.fastly.com/pricing.
Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly Engineers detected a performance impacting event affecting the Bangkok (BKK) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly Engineers detected a performance impacting event affecting the Manila (MNL) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We're currently investigating performance impacts in Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ).
All other locations and services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ) 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.
Traffic in Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ) has been temporarily rerouted.
All other locations and services are unaffected.
Our engineers are coordinating with ISPs local to the Indian region and developing an adjusted mitigation strategy to our Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ) POPs.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ) POPs has been mitigated.
The fix has been successfully deployed, and we have observed a recovery. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
We will provide a final update once the incident is fully resolved.
Engineering has confirmed that our Pune (PNQ), Varanasi (VNS), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Chennai (QAP), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ) Points of Presence (POPs) has been fully restored. Customers may have experienced increased latency from February 14th, 2026 at 13:36 UTC to February 15th, 2026 at 04:20 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 has received reports of increased 425 Too Early responses affecting users on the latest release of Google Chrome (v145). The release contained a change in how the browser handles retries for 425 responses, particularly for requests containing query parameters.
While this is not a result of a change to the Fastly platform, our Engineering team is coordinating with the Chrome team to clarify expected browser behavior and resolve this issue. In the meantime, we are evaluating server-side configuration changes to ensure seamless delivery for these requests while maintaining our security standards.
What’s next? What do I have to do?
If your users are impacted and you have dedicated IPs you may choose to temporarily disable 0-RTT, or move traffic to an IP with 0-RTT disabled until Chrome browser behavior is normalized. You may also disable HTTP/3 support to reduce the impact of this issue.
Contact Information
Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.
As part of Fastly’s global network expansion, we will be adding Vijaywada (QBI), Warrangal (QBJ) data centers to Fastly's Asia network.
Traffic served by our Vijaywada (QBI), Warrangal (QBJ) data centers will be aggregated into our India region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Vijaywada (QBI), Warrangal (QBJ) . 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"
As part of Fastly’s global network expansion, we will be adding Ambala (QAV) data center to Fastly's Asia network.
Traffic served by our Ambala (QAV) data center will be aggregated into our Asia region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Ambala (QAV). 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"
As part of Fastly’s global network expansion, we will be adding Milan (BGY) data center to Fastly's Europe network.
Traffic served by our Milan (BGY) data center will be aggregated into our Europe region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Milan (BGY) . 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.
Correction applied, this maintenance was previously miscommunicated as a new Point of Presence, this is an existing POP, and the team is merely expanding it's capacity.
Fastly will be adding capacity at our New Delhi (DEL) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 11 February 2026 at 19: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.
The scheduled maintenance has been completed.