[closed]

We are currently investigating performance issues affecting the visualization of data within Signal Sciences.

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

Fastly Engineering has deployed a fix to restore data dashboard services. We have confirmed a gradual recovery of these services and will continue to monitor until all services have been fully recovered.

Our network availability, access to our Signal Sciences console, configuration management, api services and all other Point of Presence locations are unaffected by this incident. 

This incident has been resolved.

[closed] We have updated a new certificate with new IP ranges. Customers may see their agents appear to be offline or have trouble connecting to the control plane after a DNS change was made. We recommend they allow list the Fastly public IP range if they had IP based networks controls in place previously. Please let us know about any certificate issues as they should be transient. This may also impact Signal Sciences data collectors. New events from agents may not be processed by our back end services, agents may erroneously appear to be offline, and agents may not be receiving updated rules sets. Customers may experience also delays in data available in the Signal Sciences console. 

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.

[closed]

Our teams have detected an issue that is currently impacting Signal Sciences data collectors. New events from agents may not be processed by our back end services, agents may erroneously appear to be offline, and agents may not be receiving updated rules sets. Rate limit rules may not perform as expected. Customers may experience also delays in data available in the Signal Sciences console.

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

[closed]

Our teams have identified an issue impacting the population of request data within the Signal Sciences console. 

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

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

Our teams have identified a recurring event impacting the population of request data within the Signal Sciences console. Additional investigations are being conducted to identify a fix.

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

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

We are continuing to investigate and monitor this issue as an isolated incident, please continue to send and monitor ticket updates via email (securitysupport@fastly.com) while we investigate.

Issue has been isolated and determined to be impacting customers whom have enabled SSO and have not accepted the invite sent from the console. Logging in directly from SSO will prevent customers from viewing, updating and interacting with tickets in the console. Fastly advises customers to accept the invite send from the console to resolve their issues with ticket logging and interactions.

[closed]

Fastly is aware of an expected critical vulnerability the OpenSSL project is expected to disclose in the near future. We are studying the currently available information surrounding this vulnerability and do not currently believe that Signal Sciences is vulnerable. We will continue to monitor as additional information is released and will provide our customers with more information as available.

Fastly has reviewed the initial notification from OpenSSL regarding CVE-2022-3786 and CVE-2022-3602. We have analyzed the versions of OpenSSL in use at Fastly, and verified that we do not use OpenSSL 3.x. Fastly and customer usage of Fastly services are not vulnerable to CVE-2022-3786 or CVE-2022-3602.