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.

On the 26th of December 2024 Fastly Engineering took action to prevent misuse of our WebSockets functionality through the free trial mechanism by a small number of users. As a result of this action, self-service activations of WebSockets trials on the Trials page of the Fastly Control Panel are no longer available.

There is no change to the WebSockets functionality. All other products and services remain available and are unaffected by this change. 

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.

We are investigating elevated errors to websockets at our Oslo (OSL) Point of Presence (POP). 

Our engineers have identified the contributing factor and are applying a fix to our Oslo (OSL) Point of Presence (POP). 

Engineering has confirmed the impact to our Oslo (OSL) Point of Presence (POP) has been mitigated.

Engineering has confirmed that websockets at our Oslo (OSL) Point of Presence (POP) has been fully restored. Customers may have experienced inability to use websocket traffic from 14:57 on the 8th of May to 1:47 on the 9th of May UTC.

This incident is resolved.