We are investigating elevated errors to our Adelaide (ADL), Brisbane (BNE), Perth (PER) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Status Post, Created Date/Time: 2024-10-01 09:58:00 UTC 

Note: Our Customer Escalation Management team will update the start date and time of this status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Our engineers have identified the contributing factor and are applying a fix to our Adelaide (ADL), Brisbane (BNE), Perth (PER) POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Adelaide (ADL), Brisbane (BNE), Perth (PER) POPs has been mitigated.

Engineering has confirmed that our Adelaide (ADL), Brisbane (BNE), Perth (PER) POPs have been fully restored. Customers may have experienced elevated 5xx errors from 08:22 to 10:09 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" 

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" 

We're investigating possible performance impact affecting the Brisbane (BNE) data center.

All other locations and services are unaffected

Engineering has confirmed the impact to Brisbane (BNE) has been mitigated.

This event has been resolved.

Traffic in Brisbane (BNE) has been temporarily rerouted.

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

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.