Ashburn (IAD)
We're investigating elevated errors in Ashburn (IAD).
All other locations and services are unaffected
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating elevated errors in our Ashburn (IAD) and Atlanta (FTY) Point of Presence (POPs).
All other locations and services are unaffected
This issue has been identified and a fix is being implemented.
Fastly customers may have experienced failed purge requests and observed elevated 5xx errors as a result of this incident.
A fix has been implemented and we are monitoring the recovery of customer services.
This incident has been resolved.
We're currently investigating performance impacts in Europe, North America.
All other locations and services are unaffected.
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've identified possible performance impact and intermittent periods of latency affecting the Ashburn (IAD) region. Fastly Engineering has deployed standard traffic engineering practices and continue to closely monitor the region.
All other locations and services are unaffected
This incident has been resolved.
We're investigating elevated errors in Ashburn (IAD).
All other locations and services are unaffected
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're currently investigating potential impact to performance with our CDN services.
A fix has been implemented and we are monitoring the results.
We're currently investigating performance issues with our URL and Surrogate Key purging services. All other services are unaffected.
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.
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.