We are investigating elevated errors to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s.

Our engineers have identified the contributing factor and are applying a fix to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s. 

All other locations and services are unaffected.

Engineering has confirmed the impact to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s has been mitigated.

Engineering has confirmed that our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s has been fully restored. Customers may have experienced degraded performance from 19:15 to 21:45 UTC.

This incident is resolved.

We're investigating elevated errors in South America.

All other locations and services are unaffected

Fastly Engineering has observed elevated errors across multiple Points of Presence (POPs) in the region of South America.

This has been identified as an issue with a third party service provider unrelated to Fastly's Edge Cloud Platform, and a fix is being implemented. 

All other locations and services are unaffected.

Traffic in Lima(LIM) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly Engineering has applied our standard acute incident response practices and restored our LIM POP.

Customer services have returned to pre-incident performance levels.

We will continue to monitor the third party service provider issue for recovery. All locations and other services remain unaffected.

This incident has been resolved.

We’re currently investigating performance issues with Compute@Edge configuration propagation. All other services are unaffected.

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

Our investigations have identified common network provider issues related to the performance impact for our Compute@Edge services and NGWAF@Edge updates and decision making. Existing rules are operational, but new data is parsed at a slower pace. Fastly Engineering is in the process of performing standard traffic engineering to restore Compute@Edge and NGWAF@Edge services to pre-incident levels. 

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

Fastly has performed traffic engineering to route around the global network provider currently experiencing impact. Our Compute@Edge and NGWAF@Edge services are performing at pre-incident levels. 

This incident is resolved.

We're currently investigating potential impact to performance with our CDN services.

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

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 Fastly 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.

We're currently investigating potential impact to performance with our CDN services.

The 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.