Fastly favicon

Fastly outage on 2026-10-29

fastlystatus.com
October 2026 29 Minor incident

Fastly's own status page logged two separate points of presence running elevated errors on 29 October 2026, in Queretaro (QRO) and McAllen (MFE). The Queretaro incident ran 1h 58m and the McAllen one 40m, both in Fastly's North American network, and both were Fastly-side faults.

Started

02:04 UTC

Duration

Lasted 1h 58m

Source

IsDown

Next time

Fastly is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: North America, Queretaro (QRO)

What happened?

Fastly reported two incidents on 29 October 2026, both affecting North American points of presence. The first began at 02:04 UTC, hitting the Queretaro (QRO) POP with elevated errors. Fastly said at 02:16 UTC that engineers believed they had identified a contributing factor and were developing a fix, and confirmed at 03:21 UTC that the impact had been mitigated, closing out at 1h 58m. The second incident started at 03:10 UTC, while the first was still unresolved, this time against the McAllen (MFE) POP, also with elevated errors and latency. That one followed the same pattern: a contributing factor identified at 03:16 UTC, mitigation confirmed at 03:34 UTC, for a total of 40 minutes. Each update on both incidents carries the line "All other products and services are unaffected by this incident", so Fastly is explicit that the scope stayed confined to those two POPs. Neither filing explains what the contributing factor actually was, so the root cause of either incident is not on the record. No user reports were filed during the window on either incident. Fastly's wording never grades these as major or minor, it simply logs investigation, mitigation and resolution timestamps, which is what this page relies on rather than any severity label.

Learning

UptimeRobot's own probes against Fastly's api-control component, run from both EU and North American regions, show 100% uptime across the 24 hour, 7 day and 30 day windows, with this incident not registered against them. That is not a contradiction. A regional POP serving elevated errors to traffic routed through Queretaro or McAllen does not necessarily touch the API control plane that external synthetic checks query, so a clean probe result and a real, user-facing routing fault inside Fastly's edge network are both true at once. This is the general shape of a CDN failure: the breakage sits in how a specific point of presence handles requests, not in whether the vendor's control API answers a health check. If your own monitoring only watches your endpoints and response codes from your side, it will not see a POP-level fault like this one unless your traffic happens to route through the affected POP and you notice the error rate climb. Fastly's 90 day history shows 21 incidents with a median duration of 3 hours 35 minutes, so a sub-two-hour regional incident like Queretaro's sits on the shorter end of what's typical for them. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.</learned> </invoke>

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.