Content Delivery (CDN)
We're investigating possible performance impact affecting the Content Delivery (CDN) data center.
All other locations and services are unaffected.
We have identified an issue with how our systems are processing requests that involve setting querystring parameters from custom VCL using the querystring API. This is causing an increase to origin for requests that have querystring parameters with an empty value.
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 deployed a fix and have confirmed a gradual recovery for customers with a custom VCL using the querystring API. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
As this mitigation deploys throughout our fleet, customers who believe their services to be impacted may reach out to our Support team by emailing support@fastly.com. Our team has been provided with workaround that will can be deployed to prevent impact for the duration of our response to this event.
All other products and services remain unaffected by this incident.
Our engineering team deployed a fleet-wide mitigation strategy to correct the issue. Customers confirmed to be impacted by this incident and who implemented the temporary mitigation measures provided on October 7th were not affected after that point.
For all other affected customers, the issue was fully resolved by 09:45 UTC on October 9th.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-10-07 16:33:08 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.
As a part of our continued effort to enhance network efficiency across our platform, Fastly will be performing maintenance on our network management services beginning on Monday, the 30th of September 2025 at 17:00 UTC.
Our estimated duration is 60 minutes.
What’s Changing?
We will be deploying new updates to our network access control management system. This change will allow our backend systems that handle internal traffic management to communicate more efficiently and securely. During this maintenance, customers can expect minimal disruption to the Fastly Control Panel or API as these changes are being deployed.
All other services remain unaffected by this maintenance.
What’s next? What do I have to do?
Nothing. All actions taken during this planned maintenance belong to Fastly.
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.The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
We're investigating possible performance impact affecting device detection variables within our Content Delivery (CDN) service.
All other locations and services are unaffected.
Our engineers have identified the contributing factor and are developing a fix to our Content Delivery (CDN) service.
All other locations and services are unaffected.
Engineering has confirmed the impact to Content Delivery (CDN) service has been mitigated.
Engineering has confirmed that our Content Delivery (CDN) service
has been fully restored. Customers may have experienced issues with device detection variables that impacted how content was displayed on mobile devices from 16:30 to 18:45 UTC.
This incident is resolved.
To offer feedback on our status page, click " Give Feedback "
Status Post, Created Date/Time: 2025-08-07 18:38:57 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.
On the 6th of November 2024 at 20:00 UTC, Fastly began to make changes to our device detection library. Our Engineers had identified that these changes would impact a portion of the client variables used in some customer’s custom VCL code. Additionally, as part of this process we have also begun to deprecate a small portion of less frequently used variables.
Customers identified to have services impacted by this change, would have received an email notification with additional details.
- Refer to subject line, [Action Required] Changes to Device Detection Library
- Identified customers should have received messaging on the 4th of October, the 6th of December, and the 19th of December
- A status post reminder was also shared on the 7th of November, reference link
Deprecated variables and changes to make:
Identify where you use the following client.* variables in your service's custom VCL.
- client.class.checker
- client.class.filter
- client.class.masquerading
- client.class.spam
- client.platform.manufacturer
- client.display.height
- client.display.width
- client.display.ppi
- client.class.downloader
- client.class.feedreader
- client.platform.ereader
- client.platform.tvplayer
If you are using any of the above deprecated variables, please remove them, or use Client Hints to fetch that information by no later than the 8th of January 2025.
The continued use of these variables after their deprecation date will result in the return of empty values when accessing the device detection library.
If you require Fastly to coordinate with you while performing the upgrade, please contact Fastly Support at https://support.fastly.com to schedule a time to switch to the new library.
Remaining client.* will continue to work with the caveat that some of the string variables will show values differently than before. Our Client request documentation will be updated with the latest variables once this change is completed.
To offer feedback on our status page, click "Give Feedback"
On the 6th of November 2024 at 20:00 UTC, Fastly began to make changes to our device detection library. Our Engineers had identified that these changes would impact a portion of the client variables used in some customer’s custom VCL code. Additionally, as part of this process we have also begun to deprecate a small portion of less frequently used variables.
Customers identified to have services impacted by this change, would have received an email notification with additional details.
- Refer to subject line, [Action Required] Changes to Device Detection Library
Deprecated variables and changes to make:
Identify where you use the following client.* variables in your service's custom VCL.
- client.class.checker
- client.class.filter
- client.class.masquerading
- client.class.spam
- client.platform.manufacturer
- client.display.height
- client.display.width
- client.display.ppi
- client.class.downloader
- client.class.feedreader
- client.platform.ereader
- client.platform.tvplayer
If you are using any of the above deprecated variables, please remove them, or use Client Hints to fetch that information by no later than the 8th of January 2025.
The continued use of these variables after their deprecation date will result in the return of empty values when accessing the device detection library.
If you require Fastly to coordinate with you while performing the upgrade, please contact Fastly Support at https://support.fastly.com to schedule a time to switch to the new library.
Remaining client.* will continue to work with the caveat that some of the string variables will show values differently than before. Our Client request documentation will be updated with the latest variables once this change is completed.