Fastly Compute
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.
We are investigating elevated errors to our KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs).
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are developing a fix for the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs)
All other locations and services are unaffected.
Engineering has confirmed the impact to the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been mitigated.
Engineering has confirmed that the impact to the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been fully restored. Customers may have experienced elevated errors and latency from 20:34 to 22:37 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-08-20 22:26:51 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 and increased latency to our Compute and Next-Gen WAF (NGWAF) services.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are developing a fix to our Compute, Next-Gen WAF (NGWAF) service.
All other locations and services are unaffected.
Our engineers have identified the primary cause and we've deployed mitigation steps for the issues impacting Compute and our Next-Gen WAF (NGWAF).
We are aware that our status post updates are not reaching dedicated customer chat channels correctly. For the most current and accurate information, please continue to follow the incident directly on our status page, through SMS or Email notifications which remain unaffected by this incident.
We're continuing to work with our incident response teams to fully restore service. We'll provide another update as soon as more information is available. All other locations and services are unaffected.
We can confirm that Compute services have been restored.
Our teams remain actively engaged in mitigating the issue affecting Next-Gen WAF (NGWAF) services. We'll continue to provide updates as soon as new information is available.
All other locations and services are unaffected.
We've confirmed that the issues impacting both our Compute and Next-Gen WAF (NGWAF) services have been mitigated.
We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
This incident has been resolved. On the 18th of August 2025, customers experienced impact to Compute services between 18:50-19:26 UTC and NGWAF services between 18:50-21:59 UTC. During these times, customers may have seen elevated errors and increased latency. Services leveraging Compute, such as certain public APIs (KV Store, Domainr, etc.), were also affected.
Separately, our CX Escalation engineers identified and resolved a vendor-related issue that prevented status updates from reaching dedicated customer chat channels during a portion of the incident. All notification systems are now fully operational.
This incident is fully resolved.
To offer feedback on our status page, click " Give Feedback "
Status Post, Created Date/Time: 2025-08-18 19:09:15 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 seeing increased errors across multiple Fastly services that utilize a common third party service provider, unrelated to Fastly's Edge Cloud Network.
Fastly has launched acute incident response practices to investigate into this issue further in an effort to reduce the impact to our customers.
As our engineers determine the scope of impact our Customer Escalation Management team will be updating the impacted components on this status post.
We're aware of an ongoing Google Cloud incident, detailed on their status page, which is affecting several Fastly services. Customers may be experiencing increased latency due to impact to our KV Store.
Specifically, those trying to access their control plane via manage.fastly.com might notice that several key Observability features are not loading, including Billing, Historical Stats, Log Explorer & Insights, Origin Inspector, Real-Time Log Streaming, and Real-time Analytics. You may also find it difficult to engage with API endpoints. Additionally, customers might see elevated errors when accessing Fastly webpages and documented resources.
Our engineers are working to restore these services as a high priority and we will provide more information shortly.
You can monitor the Google Cloud incident here:
We've confirmed that customers won't receive status post notifications through their Support Slack channels during this incident.
However, we want to assure you that your ability to request a support case through our Support Slack services remains unaffected. You can still open new support cases as needed.
Google Cloud has communicated that they have successfully deployed mitigations to the majority of their services. We are now observing a gradual recovery of Fastly services.
We will continue to monitor this situation with the highest priority until all Fastly and customer services are fully restored.
We have continued to monitor the Google Cloud Status Page for the latest information by the third party service provider.
Incident Update: Full Recovery and Root Cause Identified
Current Status: Resolved
We're confirming that all services impacted during yesterday's incident have fully recovered. Our teams continuously monitored the situation and verified the stability of all affected systems.
Root Cause Analysis
Our investigation has confirmed that the increased errors and latency across our KV Store, control plane, and certain Observability features were a direct result of the Google Cloud disruption on the 12th of June 2025.
Google has publicly shared a post-mortem regarding the incident. It includes specific information about the root cause—an invalid automated quota update to their API management system—along with their mitigation strategies and steps they're taking for future prevention.
Next Steps
For a comprehensive understanding of the incident's origin, mitigation, and Google's preventative measures, we encourage customers to review the official Google Cloud Status Page. This provides a full breakdown from their perspective.
Additionally, our Product and Engineering teams will thoroughly review all Google Cloud Platform (GCP) reports to determine mitigation strategies and ensure they are adopted as part of our long-term preventive measures to ensure our systems are more resilient to third-party outages of this kind in the future.
We appreciate your patience and understanding as we worked through this third-party event. Our focus remains on providing reliable and high-performance services.
We are investigating elevated errors to our Compute service.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are developing a fix to our Compute service.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Compute service has been mitigated.
Engineering has confirmed that our Compute service has been fully restored. Customers may have experienced errors when they attempted update WASM packages from 17:40 to 20:31 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: 2025-04-29 20:46:42 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 to our Fastly Compute service.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Fastly Compute service.
All other locations and services are unaffected.
Engineering has confirmed the impact to Fastly Compute
service
has been mitigated.
Our engineers have confirmed that our Compute services have been fully restored. During this incident new version deployments would have been prevented, but not lost. These deployments were delayed, but our customers should begin to see their updates propagate for their services now that this incident is resolved. Our investigation in to this incident shows a possible impact window of 17:08 to 18:05 UTC on the 17th of April 2025.
The duration of impact from this incident will vary across our customers.
Our ability to deliver Network services and all other products and services were unaffected by this incident.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-04-17 17:46:13 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 to our Configuration Management Services, Config Store services.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix (from/to) our Configuration Management Services, Config Store services.
All other locations and services are unaffected.
Engineering has confirmed the impact to Configuration Management Services, Config Store services has been mitigated.
Engineering has confirmed that Configuration Management Services, Config Store services has been fully restored. Customers may have experienced error responses to requests to the service configuration API with retires succeeding from 18:18 to 18:41 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-03-28 18:42:12 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 to our Secret Store service.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Secret Store service.
All other locations and services are unaffected.
Engineering has confirmed the impact to Secret Store service has been mitigated.
Engineering has confirmed that Secret Store service has been fully restored. Customers may have experienced an increase in decryption errors for secret store from 18:55 to 19:49 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-03-06 19:31:59 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.We are investigating elevated errors to our Compute and Next-Gen WAF (NGWAF) services.
All other products and services are unaffected by this incident.
Status Post, Created Date/Time: 2024-10-02 19:56 UTC
Note: Our Customer Escalation Management team will update the start date and time of this 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.
Our engineers have identified the contributing factor and are applying a fix to our Compute and Next-Gen WAF (NGWAF) services.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Compute and Next-Gen WAF (NGWAF) services has been mitigated.
Engineering has confirmed that Compute and Next-Gen WAF (NGWAF) services have been fully restored. Customers may have experienced errors when deploying Edge WAF services from 14:41 to 19:52 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"