We're investigating possible performance impact affecting the Marseille (MRS) data center.

All other locations and services are unaffected

Our engineers have identified the contributing factor and are applying a fix to Marseille (MRS) POP.

Engineering has confirmed the impact to Marseille (MRS) POP has been mitigated.

Engineering has confirmed that Marseille (MRS) POP has been fully restored. Customers may have experienced increased latency and 5xx errors from 18:50 to 19:38 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Fastly will be adding capacity at our Marseille (MRS) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 08 December 2023 at 02:00 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify 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.

Traffic in Marseille (MRS) has been temporarily rerouted.

All other locations and services are unaffected.

This issue has been identified and a fix is being implemented. 

On the 24th of August at 09:15 UTC, Fastly Engineering confirmed with a third party service provider that there is an active fiber cut within the Marseille (MRS) region that is impacting connectivity to our Point of Presence (POP). We have performed standard traffic engineering practices to route our customer services away from the impacted region.

We are actively engaged with the third party service provider and are receiving routine updates as they continue to work on the issue. Once they have reported the conditions "mitigated", we will perform some tests to verify and update our status post.

For additional questions please reach out to our Support team through https://support.fastly.com.

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