Fastly outage, November 2026: Data Center Capacity Expansion for Manchester (MAN)
Fastly is reporting an incident: Data Center Capacity Expansion for Manchester (MAN). It is still open.
!Degraded
From Fastly's official status page, in their words.
What happened
- Started
- Status
- notice
- Duration
- 1 minute so far
- Impact
- not stated
- Investigating
- Identifiednot yet
- Monitoringnot yet
- Resolvednot yet
Why it happened
Fastly has not given a cause yet. We never guess one.
Timeline
Newest first. From Fastly's official status page, in their words.
- notice
Fastly will be adding capacity at our Manchester (MAN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 10 November 2026 at 00: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.
What this means for a business
- Check whether your own website is affected before telling customers.
- Do not restart or rebuild servers to fix a provider outage; it will not help.
- Keep the status page open; providers post updates every 15 to 30 minutes during an incident.
The full guide: what to do when a service you rely on is down
Other Fastly incidents
- Upcoming change to geolocation metro code values, open, notice
- Data Center Capacity Expansion for Queretaro (QRO), open, notice
- Retrospective: Impacted Performance in Auckland (AKL), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Chicago (CHI), Columbus (CMH), Dallas (DFW), Denver (DEN), Detroit (DTW), Dubai (DXB), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Newark (EWR), Palo Alto (PAO), , resolved after 1.1 hours
- Performance Issues with https://www.fastly.com/, resolved after 8.1 hours
- Kansas City (MCI) Rerouted Traffic, resolved after 1.8 hours
Hear about the next Fastly incident as it starts
Free email alerts when the official status changes, with what to do while it is down.