Fastly experienced a major incident on July 15, 2026 affecting Asia and Singapore (SIN) and 1 more component, lasting 6h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 15, 2026, 01:41 AM UTC
We are investigating an issue causing elevated latency (high Time To First Byte (TTFB)) for our Singapore (SIN) Point of Presence (POP). Our engineers have taken steps to reduce the impact and are observing improvement while they continue to investigate the contributing factor. We will provide another update as more information becomes available or within the next hour. All other products and services are unaffected by this incident.
- investigating Jul 15, 2026, 02:40 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (SIN) 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.
- monitoring Jul 15, 2026, 02:41 AM UTC
Engineering has confirmed the impact to Singapore (SIN) POP has been mitigated.
- resolved Jul 15, 2026, 08:14 AM UTC
Engineering has confirmed that Singapore (SIN) POP has been fully restored. Customers may have experienced elevated latency from 01:00 to 01:40 UTC. This incident is resolved. 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-07-15 02:17:36 UTC