As part of Fastly’s global network expansion, we will be adding Port Blair (IXZ) data center to Fastly's Asia  network. 

Traffic served by our Port Blair (IXZ) 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 Port Blair (IXZ). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

Our engineers believe they have identified contributing factor causing the issue impacting our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) POPs.

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 also investigating elevated errors at our Sambalpur (QAK) POP. 

We are investigating elevated errors to our Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) Points of Presence (POPs). 

All other products and services are unaffected by this incident.

Fastly will be adding capacity at our Rio de Janeiro (GIG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 March 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.

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 03 March 2026 at 00: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.

Our engineers believe they have identified contributing factor causing the issue impacting the Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) 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 Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) Point of Presence (POPs).

All other products and services are unaffected by this incident.

As part of Fastly’s global network expansion, we will be adding Ludhiana (QBA), Shimla (QBF), Kochi (QBO) data centers to Fastly's Asia network. 

Traffic served by our Ludhiana (QBA), Shimla (QBF), Kochi (QBO) data centers 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 Ludhiana (QBA), Shimla (QBF), Kochi (QBO). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

As part of Fastly’s global network expansion, we will be adding London (BQH) data center to Fastly's European (EMEA) network. 

This facility will initially launch as a limited availability deployment on the 26th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 00: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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

As part of Fastly’s global network expansion, we will be adding London (QQP) data center to Fastly's European (EMEA) network. 

This facility will initially launch as a limited availability deployment on the 26th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 00: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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

The Chrome team has confirmed that they've identified the contributing factor and are working to deploy a fix. 

Fastly will temporarily disable  0-RTT to limit the scope of impact for customers currently using TLS 1.3 0-RTT TLS configurations  at 19:30 UTC. 

Customers using dedicated IPs your configurations will not be changed. If you wish to disable 0-RTT for your dedicated IPs as a precaution, please contact our  Support team through  https://support.fastly.com  or by contacting your designated account management team members.

We will post a new update once the fix from the third party service provider has been released and we see signs of recovery.

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.

As part of Fastly’s global network expansion, we will be adding Surrey (LGW) data center to Fastly's European (EMEA)  network. 

This facility will initially launch as a limited availability deployment on the 25th of February 2026, meaning not all customer traffic will be routed through this new location during this initial phase. 

Our estimated duration is 4 hours, starting at 01: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 Public IP List | Fastly Documentation. 

Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.

We have released an update to the Fastly status page that introduces private notifications for security maintenance and incidents. To access these private components and their detailed alerts, you may sign into www.fastlystatus.com using your existing manage.fastly.com credentials.

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

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 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.

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.

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.

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.

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.

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.

Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (SIN) Point of Presence (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.

We are investigating elevated errors to our Singapore (SIN) Point of Presence (POP).

All other products and services are unaffected by this incident.