We're investigating possible performance impact affecting the Adelaide (ADL) data center.

All other locations and services are unaffected.

Our engineers are continuing to investigate possible performance impact to Adelaide (ADL) POP.

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are developing a fix to our Adelaide (ADL) POP.

All other locations and services are unaffected.

Engineering has confirmed the impact to Adelaide (ADL) POP has been mitigated.

Engineering has confirmed that Adelaide (ADL) POP has been fully restored. Customers may have experienced performance issues resulting in some errors from 11:15 to 14:11 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-07-23 13:49:33 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" 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.

Fastly will be adding capacity at our Adelaide (ADL) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 July 2025 at 16: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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly Engineers detected a performance impacting event affecting the Adelaide (ADL) data center.

Customers may have experienced periodic intermittent errors between the times of 07:58 to 08:20 UTC, 09:15 to 10:35 UTC and 11:15 to 11:30 UTC. 

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

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" 

Traffic in our Adelaide (ADL) Point of Presence (POP) has been temporarily rerouted.

All other locations and services are unaffected.

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