Fastly outage, October 2026: [Action Required] Compute services: Shielding migration from Milan (MXP) to Milan (BGY)
Fastly is reporting an incident: [Action Required] Compute services: Shielding migration from Milan (MXP) to Milan (BGY). It is still open.
!Degraded
From Fastly's official status page, in their words.
What happened
- Started
- Status
- notice
- Duration
- 15 days 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
Our previous status post about this migration said no action was required. That was incorrect for Compute services that use mxp-milan-it as a shield location. If you have a Compute service that shields at Milan (MXP), you need to update it by November 2, 2026. Fastly can’t make this change for you because the shield location is set in your service’s code or Compute Config Store. We’re sorry for the confusion.What’s changing?Fastly is decommissioning the Milan (MXP) POP. Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield location to our Milan (BGY) POP.During this migration period, Compute services that reference mxp-milan-it will be redirected to bgy-milan-it. After the migration period ends, mxp-milan-it will no longer be a valid shield location, and Compute services that still reference it will get an error when creating the shield. How your service behaves after that depends on how your code handles that error.What’s next? What do I have to do?Compute servicesIf your Compute service uses mxp-milan-it as a shield location, update it to bgy-milan-it before November 2, 2026. We recommend making this change as soon as possible.Find every place your service sets mxp-milan-it as a shield location, including shield names in your code and any values your code loads from a config store.Replace mxp-milan-it with bgy-milan-it.If you changed your code, build and deploy a new version of your service.
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 Manchester (MAN), 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 minute
- 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.