Singapore (QPG)

Singapore (QPG) Data Center Capacity Expansion

15 February 2024, 20:00 UTC
Platform Asia Singapore (QPG)
 
15 February 2024, 20:00 UTC

Fastly will be adding capacity at our Singapore (QPG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 15 February 2024 at 20: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 (support@fastly.com).

 
16 February 2024, 00:00 UTC

The scheduled maintenance has been completed.

CDN Regional Performance Impact

07 November 2023, 11:30 UTC
Platform Asia Seoul (ICN) Singapore (QPG)
 
07 November 2023, 11:30 UTC

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

All other locations and services are unaffected.

 
07 November 2023, 16:24 UTC

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

All other locations and services are unaffected.

 
07 November 2023, 16:32 UTC

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

 
07 November 2023, 17:27 UTC

A fix has been implemented and we are monitoring the results. We are also continuing to observe this situation.

 
07 November 2023, 17:54 UTC

This incident has been resolved.

Singapore (QPG) Elevated Errors

28 July 2023, 22:17 UTC
Platform Asia Singapore (QPG)
 
28 July 2023, 22:17 UTC

We're investigating elevated errors in Singapore (QPG).

All other locations and services are unaffected

 
28 July 2023, 22:47 UTC

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

 
28 July 2023, 23:03 UTC

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

 
28 July 2023, 23:18 UTC

This incident has been resolved.

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.

Possible Performance Impact Affecting Singapore (QPG)

08 September 2022, 14:11 UTC
Platform Asia Singapore (QPG)
 
08 September 2022, 14:11 UTC

We're investigating possible performance impact affecting the Singapore (QPG) data center. All other locations and services are unaffected

 
08 September 2022, 14:33 UTC

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

 
08 September 2022, 16:47 UTC

This incident has been resolved.

Retrospective - Possible Performance Impact in Asia/Pacific (APAC) region

16 June 2022, 13:59 UTC
Chennai (MAA) Hyderabad (HYD) Hong Kong (HKG) Sydney (SYD) Kolkata (CCU) Mumbai (BOM) New Delhi (DEL) Seoul (ICN) Singapore (QPG)
 
16 June 2022, 13:59 UTC
Fastly Engineers detected a possible performance impacting event affecting the Asia/Pacific (APAC) region from approximately 2022-06-16 11:49 UTC to 2022-06-16 11:56 UTC. Customers may have seen intermittent errors for one or more data centers in this region during the impact window. All other regions and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Retrospective - Impacted Performance in Sydney (SYD), Seoul (ICN), Kuala Lumpur (KUL), Singapore (QPG), Hong Kong (HKG), and Tokyo (HND)

07 June 2022, 15:52 UTC
Hong Kong (HKG) Sydney (SYD) Kuala Lumpur (KUL) Seoul (ICN) Singapore (QPG) Tokyo (HND)
 
07 June 2022, 15:52 UTC
Fastly Engineers detected a performance impacting event affecting the Sydney (SYD), Seoul (ICN), Kuala Lumpur (KUL), Singapore (QPG), Hong Kong (HKG), and Tokyo (HND) data center from approximately 2022-06-07 14:07 UTC to 2022-06-07 14:50 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Elevated Errors in Singapore (QPG)

24 April 2022, 10:32 UTC
Singapore (QPG)
 
24 April 2022, 10:32 UTC
We're investigating elevated errors in Singapore (QPG). All other locations and services are unaffected
 
24 April 2022, 10:33 UTC
We are continuing to investigate this issue.
 
24 April 2022, 10:46 UTC
We are continuing to investigate this issue.
 
24 April 2022, 12:40 UTC
The issue has been identified and a fix is being implemented.
 
24 April 2022, 13:53 UTC
A fix has been implemented and we are monitoring the results.
 
24 April 2022, 14:21 UTC
This incident has been resolved.