Frankfurt (FRA)
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.
Fastly will be adding capacity at our Frankfurt (FRA) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 17 May 2023 at 22: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 adding capacity at our Frankfurt (FRA) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 16 May 2023 at 22: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 adding capacity at our Frankfurt (FRA) data center. End-users may observe connection resets as traffic is migrated onto new hardware.
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.
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.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue. Traffic for a subset of nodes in Frankfurt (FRA) has been temporarily rerouted. All other locations and services are unaffected.
The issue has been identified and a fix is being deployed. A subset of traffic in our Frankfurt (FRA) data center will remain on alternate routes until our fix has been fully deployed. All other locations and services are unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Fastly will be adding capacity at our Frankfurt, Germany (FRA) data center. End-users may observe connection resets as traffic is migrated onto new hardware.
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).
Maintenance will begin as scheduled in 60 minutes.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The scheduled maintenance has been completed.
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.