Los Angeles (LGB)
We're currently investigating performance impacts in Europe, North America.
Customers may experience increased errors and latency in the affected regions.
All other locations and services are unaffected.
This issue has been identified and a fix is being implemented.
After further investigation, Fastly Engineering has narrowed the scope of impact to the following POPs: Amsterdam (AMS), Stockholm (BMA), Denver (DEN), Frankfurt (FRA), London (LCY), Newark (EWR), Atlanta (FTY), Helsinki (HEL), Palo Alto (PAO), Paris (PAR), London (LHR), Atlanta (PDK), New York (LGA), Portland (PDX), San Jose (SJC), Los Angeles (LGB), Montreal (YUL), Toronto (YYZ).
Customers may continue to experience latency and errors in these POPs.
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 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.
Traffic in Los Angeles (LAX) has been temporarily rerouted.
All other locations and services are unaffected.
This incident has been resolved.
Fastly will be migrating customers shielding in Los Angeles (LGB) to Los Angeles (BUR).
Customers can either apply a new shield in advance, or their shielding configuration will be updated to Los Angeles (BUR) on their behalf during the maintenance.
When this change is applied, customers may observe additional origin traffic as cache nodes retrieve content from origin.
Action for Fastly Customers:
- Please be sure to check that your origin access lists allow the full range of Fastly IP addresses: https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges. Failure to verify origin access lists will result in origin connection disruption.
- Access the Fastly App and modify your service's shield: https://docs.fastly.com/en/guides/shielding#enabling-shielding.
- Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).
The scheduled maintenance was completed on the 30th of March at 08:00 UTC.
Fastly Engineers detected a performance impacting event affecting the Los Angeles (BUR),Los Angeles (LGB) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
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.