Asia
We are investigating elevated errors to our Manila (MNL) Point of Presence (POP) affecting customers with backends in the us-east-1 region.
All other products and services are unaffected by this incident.
We will provide another update as more information becomes available or within the next hour.
We have rerouted traffic away from our Manila (MNL) Point of Presence (POP).
Our team will continue to monitor stability and will provide an update once traffic is safely returned to MNL, until further notice.
Our engineers have confirmed that our Manila (MNL) Point of Presence (POP) has been fully restored.
Customers with backends in the us-east-1 and us-east-2 regions may have experienced elevated errors from approximately 04:22 to 08:15 UTC. We mitigated this by rerouting traffic away from MNL from 08:15 to 11:03 UTC. After traffic was returned to MNL, a brief recurrence of elevated errors occurred from 11:30 to 12:04 UTC, which has since been resolved.
Service has been fully restored.
Affected customers may have experienced impact to varying degrees and for a shorter duration than 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.
Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs).
During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected.
The issue has been resolved and we are monitoring performance closely.
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.
Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (SIN) POP.
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.
Engineering has confirmed the impact to Singapore (SIN) POP has been mitigated.
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.
Fastly will be adding capacity at our Bangkok (BKK) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 01 July 2026 at 19: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 at https://support.fastly.com.
The scheduled maintenance has been completed.
Traffic in Hong Kong (HKG) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Our Engineers have deployed standard mitigations for this impact and continue to monitor our Hong Kong (HKG) performance trends. We will provide an update once the HKG POP has been fully restored. Customers may continue to experience elevated or intermittent errors as the POP recovers.
Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Traffic in Ambala (QAA) has been temporarily rerouted.
All other locations and services are unaffected.
Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)).
All other components, locations and services were unaffected by this event.
As part of Fastly’s global network expansion, we will be adding a Riyadh (RUH) data center to Fastly's Saudi Arabia network.
Traffic served by our Riyadh (RUH) data center will be aggregated into our Saudi Arabia region for billing and stats purposes.
We expect that some traffic currently served by our data centers in neighboring regions will shift to Riyadh (RUH) . As such, some customers may see a change in their bills.
Fastly’s standard billing rates are located at https://www.fastly.com/pricing.
The scheduled maintenance has been completed.
Traffic in Dhanbad (QAM), Raipur (RPR) has been temporarily rerouted.
All other locations and services are unaffected.