Manila (MNL)

Elevated Errors for Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Seoul (ICN)

15 December 2023, 17:20 UTC
Platform Asia Kuala Lumpur (KUL) Manila (MNL) Osaka (ITM) Seoul (ICN)
 
15 December 2023, 17:20 UTC

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

 
15 December 2023, 17:54 UTC

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

 
15 December 2023, 18:12 UTC

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. 

CDN Global Performance Impact

19 January 2023, 23:05 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) 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) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) 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) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) 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)
 
19 January 2023, 23:05 UTC

We're currently investigating potential impact to performance with our CDN services.

 
19 January 2023, 23:06 UTC

A fix has been implemented and we are monitoring the results.

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.

OpenSSL - Pending Vulnerability Announcement

28 October 2022, 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) 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) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) 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) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
28 October 2022, 19:48 UTC

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.

 
01 November 2022, 17:09 UTC

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.

CDN Performance Impact

15 September 2022, 20:10 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) 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) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) 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) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
15 September 2022, 20:10 UTC

We're currently investigating potential impact to performance with our CDN services.

 
15 September 2022, 20:26 UTC

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

 
15 September 2022, 20:33 UTC

A fix has been implemented and we are monitoring the results.

 
15 September 2022, 20:47 UTC

This incident has been resolved.

Retrospective - Impacted Performance in Manila (MNL)

23 July 2022, 14:21 UTC
Manila (MNL)
 
23 July 2022, 14:21 UTC
Fastly Engineers detected a performance impacting event affecting the Manila (MNL) data center from approximately 2022-07-23 14:09 UTC to 2022-07-23 14:15 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Retrospective - Impacted Performance in Manila (MNL)

10 June 2022, 12:14 UTC
Manila (MNL)
 
10 June 2022, 12:14 UTC
Fastly Engineers detected a performance impacting event affecting the Manila (MNL) data center from approximately 2022-06-10 09:52 UTC to 2022-06-10 09:55 UTC and from 2022-06-10 11:39 UTC to 2022-06-10 11:41 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Traffic rerouted in Manila (MNL)

21 April 2022, 03:01 UTC
Manila (MNL)
 
21 April 2022, 03:01 UTC
Traffic in Manila (MNL) has been temporarily rerouted. All other locations and services are unaffected.
 
21 April 2022, 03:46 UTC
A fix has been implemented and we are monitoring the results.
 
21 April 2022, 03:59 UTC
This incident has been resolved.

Traffic rerouted in Manila (MNL)

16 December 2021, 14:09 UTC
Manila (MNL)
 
16 December 2021, 14:09 UTC
We're investigating elevated errors in Manila (MNL). All other locations and services are unaffected
 
16 December 2021, 14:38 UTC
Traffic in Manila (MNL) has been temporarily rerouted. All other locations and services are unaffected.
 
18 December 2021, 04:09 UTC
This incident has been resolved.

Traffic rerouted in Manila (MNL)

10 December 2021, 04:45 UTC
Manila (MNL)
 
10 December 2021, 04:45 UTC
Traffic in Manila (MNL) has been temporarily rerouted. All other locations and services are unaffected.
 
14 December 2021, 07:46 UTC
A fix has been implemented and we are monitoring the results.
 
15 December 2021, 08:05 UTC
This incident has been resolved.

Traffic rerouted in Manila (MNL)

09 December 2021, 02:34 UTC
Manila (MNL)
 
09 December 2021, 02:34 UTC
Traffic in Manila (MNL) has been temporarily rerouted. All other locations and services are unaffected.
 
09 December 2021, 12:23 UTC
A fix has been implemented and we are monitoring the results.
 
09 December 2021, 14:22 UTC
This incident has been resolved.