Fastly

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.

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 …

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

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.

The scheduled maintenance has been completed.

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

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.

The Chrome team has merged a fix on Google Chrome version 145.0.7632.115 or higher to address the elevated "425 Too Early" responses currently affecting users.

Following an investigation, the Chrome team has developed a fix to address a regression in the browser's retry logic. The issue was triggered when standard web requests (such as page loads or searches) included query parameters. In these cases, the browser was failing to automatically retry the request if it received a "Too Early" response from the network.

The fix ensures that these common, safe-to-retry requests are handled correctly by the browser, which will resolve the errors …

The scheduled maintenance has been completed.

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

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.

Engineering has confirmed that Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs has been fully restored. Customers may have experienced elevated errors from 09:15 to 12:35 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.

Engineering has confirmed the impact to Kolkata (CCU), Mumbai (BOM), New Delhi (DEL) POPs has been mitigated.

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.

Maintenance was completed on February 24, 2026 - this function is fully available.

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

The scheduled maintenance has been completed.

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

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

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 …

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 scheduled maintenance has been completed.

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

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

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.

As applicable, private component status updates will automatically route to your provide #fastly-{{customer}} support chat channel without any further action being required by our customers. Support teams can help you unsubscribe at the support chat channel level should you wish to be omitted from these notifications.

The scheduled maintenance has been completed.

This event has been resolved.

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

This incident has been resolved.

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.

This incident has been resolved.

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.

This event has been resolved.

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.

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) …

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), …

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 …

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 …

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), …

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

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.

If your …

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

We are investigating elevated errors to our Content Delivery (CDN) service.

All other products and services are unaffected by this incident.

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.

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.

As part of Fastly’s global network expansion, we will be adding New Delhi (DEL) data center to Fastly's Asia-Pacific (APAC) network. 

Traffic served by our New Delhi (DEL) data center 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 New Delhi (DEL). 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 …

This event has been resolved.

Engineering has confirmed the impact to Singapore (SIN) POP has been mitigated.

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.

This event has been resolved.

Traffic in Singapore (SIN) 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.

Fastly Engineers detected a performance impacting event affecting the Tokyo (TYO) data center.

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

The scheduled maintenance has been completed.

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

We are scheduling updates to the Fastly status page for February 24, 2026 to enable private notifications for security maintenance and incidents.

This update will not change your current support experience. You will continue to receive alerts in your #fastly-(customer) Slack channel without interruption.

If you are interested in learning more, our support and account teams have an FAQ available regarding these upcoming changes. We will also release a blog post and update our status page documentation following the conclusion of this maintenance.

Our engineers are conducting scheduled maintenance to decommission the TYO (Tokyo) POP. This update will help to consolidate our network footprint in the Tokyo region. To learn more about shielding concepts, please read:https://docs.fastly.com/en/guides/shielding.

We are decommissioning the TYO POP to consolidate our presence in the region. The new location name for origin shielding has changed from tyo-tokyo-jp to nrt-tokyo-jp.

Customers who have met the condition of currently utilizing TYO for their Origin Shield should perform Shielding Migration by March 26th, 2026 in order to avoid potential shielding failures or fallback to …

Our engineers are conducting scheduled maintenance to decommission the QPG (Singapore) POP. This update will help to consolidate our network footprint in the Singapore region. To learn more about shielding concepts, please read: https://docs.fastly.com/en/guides/shielding.

We are decommissioning the QPG POP to consolidate our presence in the region. The new location name for origin shielding has changed from “Singapore (QPG) - qpg-singapore-sg” to “Singapore (SIN) - sin-singapore-sg”.

Customers who have met the condition of currently utilizing QPG for their Origin Shield should perform Shielding Migration by March 26th, 2026 in order to …

This event has been resolved.

As final mitigations occurred, customers attempting to update configurations from 19:48 to 20:03 UTC may have also seen an error. Telemetry confirmed a final small window of possible impact.

Our engineers are completing a full retrospective of this incident, customers who would like the full Fastly Service Advisory may reach out to our Support team to ensure a copy is provided once completed.

As part of Fastly’s global network expansion, we will be adding Delhi-Vikaspuri (HDO) data center to Fastly's Asia network. 

Traffic served by our Delhi-Vikaspuri (HDO) 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  Delhi-Vikaspuri (HDO). 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 with elevated errors for the manage.fastly.com and API.  Customers may have experienced elevated 5xx/4xx errors when attempting configuration updates from 13:38 to 13:52 UTC.

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

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

This event has been resolved.

Engineering has confirmed that the Fastly Application component has been fully restored. Customers may have experienced elevated 5xx/4xx errors when attempting configuration updates from 18:36 UTC on Monday 9 February 2026 to 03:45 UTC on Tuesday 10 February 2026 .

We have reopened this incident as our engineers have identified some lingering effects impacting a small subset of requests. While we have already seen a broad recovery, we are deploying additional mitigations to ensure that configuration updates are fully restored for all customers.

We are continuing to monitor the situation closely and will provide another update once we have confirmed that all customer services are back to 100% functionality.

Impact:

Customers may still experience intermittent 5xx/4xx errors when attempting to make configuration updates via manage.fastly.com or the API. Existing services remain unaffected and continue to operate normally.

Engineering has confirmed that Fastly Application (manual and API configurations) has been fully restored. Customer would have experienced elevated 4xx/5xx errors when attempting to activate (new) or update their service configurations within www.manage.fastly.com from 18:36 UTC to 20:21 UTC.

This incident is resolved.

Affected customers would have experienced impact to varying degrees and to a shorter duration than as set forth above.

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 …

Engineering has deployed a fix and have confirmed a gradual recovery to both manual configuration update and those made via API request. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

This incident did contain network impact, in that configuration updates could not be made. However, our ability to deliver network and security services for active configurations were unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application 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 Kolkata (CCU) has been temporarily rerouted.

All other locations and services are unaffected.

We are investigating elevated errors to our Fastly Application services.

All other products and services are unaffected by this incident.

The scheduled maintenance has been completed.

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

Fastly will be adding capacity at our Houston (IAH) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 07 February 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.