We are investigating elevated errors to our Platform delivery services.

Our engineers are continuing to investigate the impact to our Platform delivery services.

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 UTC.

This incident is resolved.

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

To offer feedback on our status page, click "Give Feedback" 

Fastly Engineers detected a performance impacting event affecting the Seoul (ICN) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly Engineers detected a performance impacting event affecting the Seoul (ICN) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Traffic in Seoul (ICN) has been temporarily rerouted.

All other locations and services are unaffected.

We are investigating elevated errors to our Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs.

Engineering has confirmed the impact to Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs has been mitigated.

Engineering has confirmed that Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs have been fully restored. Customers may have experienced elevated errors and latency from 17:38 to 18:13 UTC.

This incident is resolved.

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

We are investigating elevated errors to our Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Seoul (ICN) point of presence (POPs).  

Engineering has confirmed the impact to Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Seoul (ICN) POPs has been mitigated.

Engineering has confirmed that the elevated errors to the Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Seoul (ICN) POPs has been fully restored by a 3rd party cloud provider. Customers may have experienced elevated 503 errors from 16:11 to 17:50 UTC.

This incident is resolved.

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

Updated

18th December 2023 - a retrospective investigation performed by engineers confirmed an earlier start time of 16:11 UTC on the 15th of December than originally communicated on our status page during acute incident response practices. 

We're currently investigating performance impacts in Seoul (ICN), Singapore (QPG).

All other locations and services are unaffected.

We're still actively investigating performance impacts between Seoul (ICN), Singapore (QPG) and the North America region. 

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. We are also continuing to observe this situation.

This incident has been resolved.

We're investigating elevated errors in Seoul (ICN).

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.

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.