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" 

We are excited to share that the AI Accelerator is now available to all customers as part of our continuous efforts to leverage and optimize AI across our fleet. We’ve heard your feedback and have added additional configurability and extended the supported Large Language Models (LLM) to include OpenAI, Azure OpenAI, Gemini, and other LLMs with OpenAI-compatible APIs. 

For more information, please read our page for how to speed up responses and data processing for AI applications with Fastly. 

I am a beta user. What do I have to do?

Beta access to the AI Accelerator will remain active and all test code will continue to work through the 15th of January 2025.

To continue using the AI Accelerator post-beta, you can navigate to the AI Accelerator landing page on the web interface in the Fastly Application (Select Tools > AI Accelerator) to purchase the product and ensure access beyond the beta grace period. 

If you do not elect to purchase the AI Accelerator product, your access will be revoked and all existing items written within the beta period will no longer be available after the 16th of January 2025.

Contact Information

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.

Customer Messaging

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.

We are investigating elevated errors to our https://www.fastly.com/ service. New customers that are attempting to create new accounts may experience errors during the account creation process.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our https://www.fastly.com/ service.

All other locations and services are unaffected.

Engineering has confirmed the impact to our https://www.fastly.com/ service has been mitigated.

Engineering has confirmed that our https://www.fastly.com/ service has been fully restored. New customers may have experienced elevated errors during the account creation process from the 24th of October 2024 at 00:54 UTC to the 31st of October 19:19 UTC.

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: 2024-10-31 18:17:33 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.

We are investigating elevated errors when attempting to access https://developer.fastly.com.

Our engineers have identified the contributing factor and are applying a fix to our https://developer.fastly.com service.

All other locations and services are unaffected.

Our engineers are continuing to investigate elevated errors when attempting to access our https://fiddle.fastly.dev webpage.

We have confirmed that https://developer.fastly.com, https://docs.fastly.com and other locations where a Fiddle example has been embedded to demonstrate example configurations are impacted by this incident, and are currently not accessible.

Customers attempting to access example configurations from our web pages or test configurations on our Fiddle webpage will experience blank fields as a result of this incident. Additionally, configurations shared by our Account teams with our customers, used on the Fiddle platform to demonstrate their effectiveness, are currently not accessible.

We are investigating this incident with a high priority, there is no impact to our network availability and all other Fastly products and services are unaffected.

Engineering has confirmed the impact to https://fiddle.fastly.dev webpage has been mitigated.

Engineering has confirmed that https://fiddle.fastly.dev webpage has been fully restored.

Customers may have experienced https://developer.fastly.com, https://docs.fastly.com and other locations where a Fiddle example has been embedded to demonstrate example configurations being inaccessible or returning blank fields from 15:21 to 20:22 UTC.

This incident is resolved.

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

Rust has recently deployed a new version, v1.80.

• Shared on their blog: https://blog.rust-lang.org/2024/07/25/Rust-1.80.0.html 

Our teams are currently in the process of upgrading our Rust SDK to be fully compatible with Rust v1.80. Until completed, we are asking our customers to please remain on v1.79.0 until we’ve released a new version of the SDK.

We expect this release will ship within several business days, this release will be shared via our standard practices on: https://docs.rs/fastly/latest/fastly/ 

Fastly has been alerted to an external outage impacting Windows-based systems. 

All our products and services remain unaffected.

Fastly is actively monitoring the situation for any potential impact to customers.

We have recently posted a thread on the Fastly Community Forum to ask for your feedback on the `fastly.toml` package manifest format as we look to design a new version that more effectively serves the needs of Compute developers: 

• https://community.fastly.com/t/have-your-say-on-the-future-of-fastly-toml/2785  

We invite you to join the discussion and appreciate your insight on how these decisions should be made.