Oceania

16 December 2024, 14:00 UTC
Platform Oceania Sydney (WSI)
 
16 December 2024, 14:00 UTC

As part of Fastly’s global network expansion, we will be adding Sydney (WSI) data center to Fastly's APAC network. 

Traffic served by our Sydney (WSI) data center will be aggregated into our APAC region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Sydney (WSI). As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https:/www.fastly.com/pricing.

 
16 December 2024, 18:00 UTC

The scheduled maintenance has been completed.

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

15 November 2024, 08:10 UTC
Platform Oceania Adelaide (ADL)
 
15 November 2024, 08:10 UTC

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

14 November 2024, 14:32 UTC
Platform Oceania Adelaide (ADL)
 
14 November 2024, 14:32 UTC

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

13 November 2024, 13:01 UTC
Platform Oceania Adelaide (ADL)
 
13 November 2024, 13:01 UTC

Traffic in Adelaide (ADL) has been temporarily rerouted.

All other locations and services are unaffected.

Platform Oceania Adelaide (ADL)
 
13 November 2024, 12:02 UTC

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.

Platform Oceania Adelaide (ADL) Brisbane (BNE) Perth (PER)
 
01 October 2024, 08:22 UTC

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.


 
01 October 2024, 10:02 UTC

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.

 
01 October 2024, 10:25 UTC

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

 
01 October 2024, 10:38 UTC

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

25 September 2024, 16:09 UTC
Platform Oceania Adelaide (ADL)
 
25 September 2024, 16:09 UTC

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

All other locations and services are unaffected.

05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dubai (FJR) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Sydney (SYD) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Wellington (WLG) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Milan (MXP) Singapore (QPG) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Tokyo (HND) Denver (DEN) Paris (CDG) Tokyo (NRT) Detroit (DTW) Paris (PAR) Rome (FCO) Tokyo (TYO) Gainesville (GNV) Sofia (SOF) Honolulu (HNL) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

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

 
05 September 2024, 22:01 UTC

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

 
05 September 2024, 23:00 UTC

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

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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

16 August 2024, 06:10 UTC
Platform Oceania Melbourne (MEL)
 
16 August 2024, 06:10 UTC

We are investigating elevated errors to our Melbourne (MEL) Point of Presence (POP).

 
16 August 2024, 07:46 UTC

Engineering has confirmed the impact to Melbourne (MEL) POP has been mitigated.

 
16 August 2024, 07:58 UTC

This event has been resolved.

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

Platform North America Asia Oceania Melbourne (MEL) Seoul (ICN) Tokyo (TYO) Los Angeles (BUR)
 
22 May 2024, 17:38 UTC

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

 
22 May 2024, 18:23 UTC

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


 
22 May 2024, 18:32 UTC

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

 
22 May 2024, 18:36 UTC

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.