Fastly incident

Elevated Errors for Singapore (QPG)

Resolved after 1 hour 36 minutes, affecting Asia and Singapore (QPG) and 1 more, on October 13, 2026.

resolved Oct 13, 2026, 04:26 AM UTC

Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors from 2:50 to 3:53 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-10-13 03:46:16 UTC

Started
Oct 13, 2026, 02:50 AM UTC
Resolved
Oct 13, 2026, 04:26 AM UTC
Duration
1h 36m
Detected by Pingoru
Oct 13, 2026, 02:50 AM UTC

Affected components

AsiaSingapore (QPG)PlatformAsiaPlatformPlatformPlatformPlatformPlatformSingapore (QPG)

Update timeline

  1. investigating Oct 13, 2026, 03:41 AM UTC

    We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP). All other products and services are unaffected by this incident.

  2. investigating Oct 13, 2026, 04:05 AM UTC

    Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (QPG) status page component. We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery. All other products and services are unaffected by this incident.

  3. monitoring Oct 13, 2026, 04:06 AM UTC

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

  4. resolved Oct 13, 2026, 04:26 AM UTC

    Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors from 2:50 to 3:53 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-10-13 03:46:16 UTC

Your product runs on more than Fastly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →