We are investigating elevated errors to our Compute services impacting new Compute activation deployments. Currently active Compute deployments remain unaffected by this incident.

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate activations on our Compute services. We have not yet identified the root cause but are actively working on diagnostics. We will provide another update as soon as we have more information.

Our engineers believe they have identified a contributing factor causing the issue impacting the Compute 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.

The fix has been successfully deployed, and we have observed a recovery of Compute activations. Error rates and latency have returned to nominal levels.

Our team will continue to monitor the platform to ensure stability before we resolve this incident.

We will provide a final update once the incident is fully resolved.

Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our Compute services. 

All other locations and services are unaffected.

A new fix has been successfully deployed, and we have observed a recovery of Compute activations. 

Our team will continue to monitor the platform to ensure stability before we resolve this incident.

We will provide a final update once the incident is fully resolved.

Engineering has confirmed that activations for our Compute services has been fully restored. Customers may have experienced elevated errors when deploying new activations from 16:13 to 22:06 UTC.

Existing services already deployed were unaffected by this incident.

This incident is resolved. All services are now operating normally.

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

Status Post, Created Date/Time: 2025-11-03 17:57:17 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 issuing an urgent advisory regarding an incompatibility between Compute services and the newly released Rust version 1.91.

Action Required 

We strongly recommend that you DO NOT upgrade to Rust version 1.91 at this time.

What Happened

We first identified this incompatibility in our testing environment on the 30th of October 2025, and have since confirmed the same Compute crash behavior in our production environment.

• Incompatible Version: Rust 1.91

• Compatible Version: Rust 1.90 and below (Previous Stable Versions)

• Impact: Using Rust 1.91 with Compute may lead to crash behavior, which will impact your traffic on Fastly.

What’s next? What do I have to do?

If you have already upgraded your services to Rust version 1.91, you must immediately downgrade to the previous stable and compatible version, Rust version 1.90, to prevent or resolve any impact to your traffic.

We are actively working on a fix to ensure compatibility with Rust version 1.91 and will provide an update as soon as a fix is available. Thank you for your patience and understanding.

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 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 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 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" 

Our engineers detected an unplanned event that contained impact to our Compute service. 

This event is resolved, and there is no remaining impact.

Customers may have experienced delays in change requests to configurations on Compute from 17:29 to 17:46 UTC. (~17min duration)

All other Compute requests remain unaffected during the impact duration.  

Please engage with our Support team through https://support.fastly.com if you have any questions and/or concerns.

Fastly engineers are currently investigating into intermittent WebSocket Connections. Customers attempting to connect to WebSocket services may experience intermittent periods of elevated errors.

All other Fastly products and services are unaffected.

Our engineers have identified the issue and are applying a fix to WebSocket Connection services.

All other Fastly products and services are unaffected.

Engineering has deployed a fix and have confirmed a gradual recovery for WebSocket Connection services. We will continue to monitor until we’ve confirmed that the service has been fully restored.

All other Fastly products and services remain unaffected by this incident.

Engineering has confirmed that WebSocket Connection services has been fully restored. Customers may have experienced intermittent periods of elevated errors from the 6th of March 10:00 to the 9th of March 04:49 UTC.

This incident is resolved.

Upcoming maintenance affecting Fanout Metrics.

Customers of Fanout may experience inaccuracies with the HTTP connections metric. HTTP Connections may be undercounted by 1 minute per connection (this would only affect Fanout, not Websockets).

The scheduled maintenance has been completed.

Fastly engineers are currently investigating into intermittent Fanout and WebSocket Connections. Customers attempting to connect to Fanout and WebSocket services may experience elevated errors.

All other Fastly products and services are unaffected.

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.