Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com.

CDN delivery, stats aggregation, and all other data plane services were unaffected.

The issue has been resolved and we are monitoring performance closely.

We're investigating an issue causing a performance impact to Next-Gen WAF (NGWAF) service.

Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour.

All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) 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 Next-Gen WAF (NGWAF) service has been mitigated.

Engineering has confirmed that Next-Gen WAF (NGWAF) service has been fully restored. Customers may have experienced a delay in propagation of new rules to NGWAF from 13:50 UTC on the 3rd of January 2026 to the 6th of January 2026 20:12 UTC. Existing NGWAF rules were not impacted. 

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: 2026-01-06 19:37:27 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 Madrid (TOJ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 24 December 2025 at 03: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" 

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

Traffic served by our  Visakhapatnam (VTZ)  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  Visakhapatnam (VTZ) . 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" 

Fastly will be adding capacity at our Atlanta (PDK) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 19 December 2025 at 06:00 UTC.

Our estimated duration is 8h. 

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 Curitiba (CWB) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 December 2025 at 08: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" 

Traffic in Vancouver (YVR) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly Engineers detected a performance impacting event affecting the Edge Observer service. Media shield customers would have experienced a loss of access to the media shield dashboard in the Observability UI from 13:41 UTC on the 16th of December 2025 to 20:04 UTC on the 17th of December 2025. 

All other data centers and services were unaffected.

The issue has been resolved and we are monitoring performance closely.

Traffic in New York (LGA) has been temporarily rerouted.

All other locations and services are unaffected.

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

Traffic served by our Anantapur (PUT) 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 Anantapur (PUT). 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 "