Tokyo (TYO)
We are aware of a possible issue and are working to determine the scope and impact.
Update: Our investigations confirmed that there were no external impacts to our customer services or end user experiences. We've changed this status from "degraded performance" to "informational".
Our Engineering team had identified an internal issue that had risk for customer impact. Our Acute Incident Response teams have deployed a fix and are monitoring the results.
Our network availability and all other locations were unaffected by this incident. Customers and their end users should not have seen impact as a result of this incident.
This incident has been resolved.
Traffic in Tokyo (TYO) has been temporarily rerouted.
All other locations and services are unaffected.
This incident has been 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.