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.

We're currently investigating performance issues with our Image Optimization service and elevated errors in our SJC POP.

All other services are unaffected.

Fastly Engineering is continuing to investigate performance issues in our San Jose (SJC) POP. Customers being serviced from this POP may be experiencing elevated errors from our network and image optimization services.

All other locations 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.

Fastly will be adding capacity at our San Jose (SJC) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 27 April 2023 at 08:00 UTC.

• Our estimated duration is 4h 

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).

The scheduled maintenance has been completed.

Fastly will be migrating Palo Alto, California (PAO) shield customers to Santa Clara, California (SJC).

As part of this migration, customers utilizing shielding in Palo Alto, California (PAO) will be migrated to Santa Clara, California (SJC). Once this maintenance window closes, customers can either apply a new shield at a time of their choosing, or their shielding configuration will be updated to Santa Clara, California (SJC) on their behalf after 14 days.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin.

Action for Fastly Customers:

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

2. Customers with any questions or concerns should contact their dedicated technical account team or Fastly's Support team at (support@fastly.com).

Thank you!

The scheduled maintenance has been completed.

We're investigating elevated errors in San Jose (SJC).

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.