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. 

To request activation of WebSockets for your account, please contact Fastly Support at https://support.fastly.com/.

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.