Singapore (QPG)

Platform Compute North America Fastly Compute Asia KV Store Singapore (QPG) Singapore (SIN) Palo Alto (PAO) San Jose (SJC)
 
20 August 2025, 20:34 UTC

We are investigating elevated errors to our KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs).

All other products and services are unaffected by this incident.

 
20 August 2025, 22:42 UTC

Our engineers have identified the contributing factor and are developing a fix for the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs)

All other locations and services are unaffected.

 
20 August 2025, 22:54 UTC

Engineering has confirmed the impact to  the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been mitigated.

 
20 August 2025, 23:03 UTC

Engineering has confirmed that the impact to the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been fully restored. Customers may have experienced elevated errors and latency from 20:34 to 22:37 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-08-20 22:26:51 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.


Platform Asia Singapore (QPG)
 
12 August 2025, 00:27 UTC

Fastly Engineers detected a performance impacting event affecting the Singapore (QPG) data center.

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

13 November 2024, 03:50 UTC
Platform Asia Singapore (QPG)
 
13 November 2024, 03:50 UTC

We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP).

All other products and services are unaffected by this incident.


 
13 November 2024, 04:38 UTC

Our engineers have identified the contributing factor and are applying a fix to our Singapore (QPG) POP.

All other locations and services are unaffected.

 
13 November 2024, 05:02 UTC

Engineering has confirmed the impact to Singapore (QPG) POP has been mitigated.

 
13 November 2024, 05:26 UTC

Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors or latency from 03:50 to 04:51 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-11-13 04:35:37 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.


Platform Asia Bangkok (BKK) Singapore (QPG)
 
09 October 2024, 02:03 UTC

We are investigating elevated errors to our Singapore (QPG), Bangkok (BKK) Points of Presence (POPs).

All other products and services are unaffected by this incident.


 
09 October 2024, 02:05 UTC

Our engineers have identified the contributing factor and are applying a fix to our Singapore (QPG), Bangkok (BKK) POPs. Our Singapore (QPG) POP has begun to show signs of recovery.

All other locations and services are unaffected.

 
09 October 2024, 02:35 UTC

Engineering has confirmed the impact to our Singapore (QPG), Bangkok (BKK) POPs has been mitigated.

 
09 October 2024, 02:36 UTC

Engineering has confirmed that our Singapore (QPG), Bangkok (BKK) POPs have been fully restored. Customers may have experienced elevated errors, latency, and timeouts from 01:30 to 2:10 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

Status Post, Created Date/Time: 2024-10-09 02:05:18 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.


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

14 August 2024, 02:05 UTC
Platform Asia Singapore (QPG)
 
14 August 2024, 02:05 UTC

We are investigating performance impacts to our Singapore (QPG) Point of Presence (POP).

 
14 August 2024, 05:15 UTC

Our engineers have identified the contributing factor and are applying a fix to our Singapore (QPG) Point of Presence (POP).

All other locations and services are unaffected.

 
14 August 2024, 06:06 UTC

Engineering has confirmed the impact to our Singapore (QPG) Point of Presence (POP) has been mitigated.

 
14 August 2024, 06:08 UTC

Engineering has confirmed that our Singapore (QPG) Point of Presence (POP) has been fully restored. Customers may have experienced latency from 02:05 to 06:00 UTC.

This incident is resolved.

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

Platform Asia Singapore (QPG)
 
12 July 2024, 15:37 UTC

Fastly Engineers detected a performance impacting event affecting the Singapore (QPG) data center.

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

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.

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.

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.