As part of Fastly’s global network expansion, we will be adding Siliguri (IXB), Shillong (SHL) data centers to Fastly's Asia  network. 

Traffic served by our Siliguri (IXB), Shillong (SHL) 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  Siliguri (IXB), Shillong (SHL) . 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 Hyderabad (QBN) data center to Fastly's Asia network. 

Traffic served by our Hyderabad (QBN) 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 Hyderabad (QBN). 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.

Fastly Engineers detected a performance impacting event affecting the Osaka (ITM) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly will be adding capacity at our Singapore (SIN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 23 March 2026 at 07: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.

Fastly will be adding capacity at our Tokyo (NRT) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 March 2026 at 16: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.

To offer feedback on our status page, click "Give Feedback" 

Fastly will be adding capacity at our Manila (MNL) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 March 2026 at 17:00 UTC.

Our estimated duration is 6h. 

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" 

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.

As part of Fastly’s global network expansion, we will be adding Srinagar-Nahota (QBG) data center to Fastly's Asia network. 

Traffic served by our Srinagar-Nahota (QBG) 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 Srinagar-Nahota (QBG). 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 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.

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

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.

We are also investigating elevated errors at our Sambalpur (QAK) POP. 

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.

Engineering has confirmed the impact to our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) POPs has been mitigated.

Engineering has confirmed that our Sambalpur (QAK), Dhanbad (QAM) , Kochi (QAN), Visakhapatnam (VTZ), Ahmedabad (QAU) POPs have been fully restored. Customers may have experienced elevated errors or increased latency from 19:07 to 19:29 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.