Object Storage
We're currently investigating performance impacts in for US-East, US-West and EU-Central with Object Storage.
All other locations and services are unaffected.
Our engineers believe they have identified contributing factor causing the issue impacting the Object Storage 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 Object Storage service has been mitigated.
Engineering has deployed a fix and have confirmed a gradual recovery to Object Storage service . We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.
All other products and services are unaffected by this incident.
Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy for our Object Storage.
All other locations and services are unaffected.
A fix has been deployed to our Object Storage. Our engineers are continuing to research the contributing factors to verify that no further actions are required. We will provide another update once our investigation is complete.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Object Storage has been mitigated.
Engineering has confirmed that Object Storage has been fully restored. Customers may have experienced elevated errors from 14:59 to 20:58 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.
This incident post has been superseded, please refer to the updated post here: https://www.fastlystatus.com/incident/378503
We are investigating elevated errors to our KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions.
All other products and services are unaffected by this incident.
Our engineers believe they have identified contributing factor causing the issue impacting the KV Store, Object Storage for Asia Pacific (APAC) and South Asia regions.
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 KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been mitigated.
Engineering has confirmed that KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been fully restored. Customers may have experienced increased latency observed when accessing KV Store and Object Storage from 14:42 UTC on April 24, 2026 to 14:49 UTC on April 25, 2026 .
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.
We're investigating possible performance impact affecting the KV Store service.
Engineering has confirmed that KV Store and Object Storage services has recovered. Customers may have experienced elevated errors for these Edge storage services from 07:20 to 08:12 UTC on the 17th September 2025.
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: 2025-09-17 08:13:28 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.
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.