General Updates
From Tuesday, April 29th through Monday, May 5th, 2025, Fastly shared a status post about a series of updates performed to enhance the billing platform within the Fastly Control Panel.
As part of our continued commitment to ensure the accuracy of invoices billed for the month of May 2025, our billing team has extended our period of manual review and validation until Friday, June 6th 2025. As a result, some customers have and may continue to experience a delay when receiving their invoices.
What’s next? What do I have to do?
Please continue to reach out to billing@fastly.com if you receive your invoice and identify a discrepancy. We will work with you to resolve the issue.
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.
On the 31st of May 2025, the Customer Escalation Management team shared a notification to all customers of a recent billing system error that may have caused an additional invoice statement to be distributed to customer inboxes. This notification was sent using customer outreach tooling within our Fastly Application, accessible through manage.fastly.com, and our customers could read about this error within their Message Portal.
On the 3rd of June 2025, we found a bug within our outreach tooling. This bug would have caused the email to users with Superuser permissions to fail. Our engineering teams have identified the bug and email alerts to account Superusers will be restored for all future customer outreaches performed by the Customer Escalation Management team.
Out of an abundance of caution, to help ensure that customers do not action the duplicative invoice and double pay - we are sharing this message again on our status page.
On the 3rd of June 2025, the Customer Escalations and PMO team will implement an update to the customer Slack-based notification system. No disruption to the receipt of notifications from www.fastlystatus.com to the support chat features within Slack is anticipated as a result of this update. Furthermore, there will be no disruption to the Status Page or alteration of subscriber notification preferences.
What’s Changing?
Following a review of customer feedback regarding the display of notification receipts within their Slack channels, which are part of our Support Chat Systems, it has been noted that the extended length of status post messages impedes the location of active support case threads. Customers have reported difficulty in identifying their support cases amidst lengthy message chains.
To address this concern, a link to the status post, impacted components, and current status will now be featured in the main channel. All message body updates will be logged in threaded replies, significantly reducing the overall space occupied by our notifications.
What’s next? What do I have to do?
Nothing. Our engineers have prepared this update to release at 13:00 UTC on the 3rd of June 2025, and there is no anticipated action or impact for our customers.
As a reminder, if our customers are receiving Status Page notifications within their Slack channels that do not apply to the Fastly Products or Services enabled, customers may run the steps below to remove unwanted notifications at any time:
- From your designated slack channel, use this backslash command: /statuscast-reset-access-code
- You will then be provided with a unique access code and a URL to follow, once on the provided webpage - enter the provided access code
- You will be routed to a subscription screen designated for your Slack channel - here you may enable or disable notification preferences for your channel
Worried about missing new components added by Fastly? Don’t be, new components will default to an “enabled” status, and the steps shared earlier can be performed any time you wish to make additional alterations to your Slack channel notification preferences.
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.
As part of an initiative to enhance operational efficiency across our platform, Fastly will conduct a systematic audit of the Account Management system. This audit will involve the removal of inactive Trial accounts and their associated data.
Current Trial accounts meeting the following criteria will be permanently deleted from our systems:
- Trial Accounts exhibiting no login activity for a period of six months or greater.
- Trial Accounts demonstrating no associated traffic for a consecutive period of six months or greater.
All other account types will not be affected by this procedure.
This procedure will not impede our ability to provide services to our customers.
Customers with inquiries or concerns are encouraged to contact our Support team via email at support@fastly.com or their designated account management personnel.
To offer feedback on our status page, click "Give Feedback"
We are currently investigating elevated errors in our Fastly Application related to the recently released General Updates, Notification Center feature.
Impacted customers would have received two notifications about a new version of Fastly CLI to support Rust v.1.84. Although the message mentions an attachment, customers may will not find a "download pdf" option upon logging in.
This incident does not affect our ability to provide Fastly services. Our customers should not be experiencing any performance issues as a result of this situation.
Our engineers have identified the contributing factor and are applying a fix to our General Updates, Notification Center service.
This incident does not affect our ability to provide Fastly services. Our customers should not be experiencing any performance issues as a result of this situation.
Engineering has confirmed the impact to General Updates, Notification Center service has been mitigated.
This incident does not affect our ability to provide Fastly services. Our customers should not be experiencing any performance issues as a result of this situation.
Informational Update
We’re always trying to make it simpler to know what’s happening with the Fastly platform, so on the 12th of February 2025, look for a brand new Notification Center on your Fastly Control Panel, which you’ll recognize by the bell icon at the top of your screen. Now, any time there’s a Service Advisory for planned updates or post-incident notifications, our Escalation Management team will make sure it’s delivered directly to your Control Panel.
Pro tip: There’s even a simple download feature if you want a PDF version of a Service Advisory alert that you can share with team members in email, Slack, or other systems.
Plus, if you’re a Super User, you’ll continue to get an email notification for Service Advisories in addition to the Notification Center alert in your Control Panel. And there’s an upgrade — if you’re a Super User, now when you reply to service advisory emails, a support ticket will automatically be created. Your Escalation Manager will follow up promptly, just like always.
If you’re using our Observability platform and have set up Alerts there, don’t worry: those are staying exactly where they are, distinct from the Notification Center, so you never have to worry about getting confused which alerts are about the Fastly platform, and which alerts you’ve set up about your own services.
We hope this is one more big step towards making sure every bit of information you need for managing your Fastly services is in one convenient place, accessible through your Fastly Control Panel. And as always, if you’re logged in, you can share your feedback with us with just a click.
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
- 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 9th of January 2025, Rust will be releasing a new version of its coding language, version 1.84. Our Engineers will be performing additional research into this new version to ensure optimal compatibility with our Compute platform.
Customers identified to have services impacted by this change, would have received an email notification with additional details.
- Refer to subject line, (Action Required) Compute Services, Pending Rust Version 1.84 Release in January 2025
In order to avoid issues or disruption when attempting to build existing Compute projects, we ask that our customers with Rust-based Compute services not perform an update to Rust version 1.84 or later until you have received a software development kit (SDK) update from Fastly.
What’s Changing?
A new version of Rust is scheduled to be released on the 9th of January 2025 that has not been fully vetted by our Engineers to ensure that the version is supported on our Compute platform.
What’s next? What do I have to do?
In accordance with our standardized best practice, customers who have Rust-based Compute services should update their Fastly CLI to the latest version (v10.17.0), or later, in order to run adequate checks on your version of Rust and compatibility with Compute, before building and deploying your code to the platform.
Our engineers are currently evaluating the upcoming Rust release (v1.84), and will release a subsequent SDK update once 1.84 platform compatibility is confirmed.
Additionally, if you are using the Rust toolchain in your CI pipeline, then you will also need to apply an upper bound for Rust at v1.83 as well.
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.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.