Fastly experienced a major incident on September 1, 2026 affecting Asia and Manila (MNL) and 1 more component, lasting 10h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 01, 2026, 06:13 AM UTC
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.
- monitoring Sep 01, 2026, 08:19 AM UTC
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.
- resolved Sep 01, 2026, 04:16 PM UTC
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. Status Post, Created Date/Time: 2026-09-01 06:18:44 UTC