[closed]

Fastly is investigating possible performance impact to NGWAF Rule and IP List updates.

Customers may experience intermittent delays when applying changes to their rules and/or IP list.

All other services are unaffected. 

Fastly engineers have deployed mitigation measures and services are available. Customers may continue to experience intermittent periods of delays, and Fastly will continue to monitor NGWAF rules and IP list services for stability. 

All other services are unaffected. 

For additional information, or to report additional impact, please contact support at https://support.fastly.com. 

[closed]

Fastly Engineering observed the NGWAF decisioning engine not checking new requests against customer rules. New IP flags are also delayed during this time.

All other services are unaffected.

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

This incident has been resolved.

[closed]

From 15 June 2023, 19:48 UTC to 15 June 2023, 20:20  UTC Fastly Engineering observed the NGWAF decisioning engine not check new requests against customer rules. New IP flags were also delayed during this time. All other services during this time were unaffected.

[closed]

Fastly is currently experiencing issues with NGWAF GeoIP country identification. Customers may experience instances in which NGWAF  labels requests with an incorrect region. For further information, please contact support@fastly.com.

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] 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 impacts Signal Sciences data collectors beginning at 00:53 UTC. Agents may appear offline in dashboard/API, agents will not receive rule updates; rate limit rules, templated rules and sites alerts will not take new traffic into account; new traffic will not appear in the dashboard/API. Customers may experience 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.

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.