Fastly favicon

Fastly outage on 2026-10-31

fastlystatus.com
October 2026 31 Minor incident

Fastly's content delivery service in its Osaka (ITM) and Tokyo (NRT) Points of Presence ran with increased errors and latency for 3h 21m on 31 October 2026. Fastly's own status page confirms the fault sat on its side, in the two Asia POPs, not in anything you control.

Started

19:19 UTC

Duration

Lasted 3h 21m

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: Asia, Osaka (ITM), Tokyo (NRT)

What happened?

Fastly logged one incident on this day, affecting the Osaka (ITM) and Tokyo (NRT) Points of Presence, both listed under the Asia region. It started at 19:19 UTC and ran for 3h 21m. Fastly's first update said engineers were investigating increased errors and latency for the content delivery service in those two POPs, and that an update would follow within the hour. At 21:20 UTC Fastly said its engineers believed they had identified the contributing factor, and that a fix was being developed, with no explanation of what that factor was. That update also noted that all other products and services remained unaffected. The last update, at 22:18 UTC, said the fix had been deployed, that error rates and latency had returned to nominal levels, and that Fastly's team would keep monitoring the platform before closing the incident out. No further update was filed after that, and no user reports were logged in this window. Fastly's status page does not say why the ITM and NRT POPs were affected or what the contributing factor actually was. Across the last 90 days Fastly has logged 21 incidents with a median duration of 3 hours 35 minutes, so this one ran close to that typical length. Over its lifetime Fastly has logged 1011 incidents, averaging 13 a month.

Learning

UptimeRobot's own probes, watching Fastly's api-control component from EU and NA regions, show 100% uptime over the past 24 hours, 7 days and 30 days, and this incident was not registered against them. That is not a contradiction. The probes check a control-plane endpoint from outside Asia, while the fault sat inside two specific delivery POPs in Osaka and Tokyo, affecting the routing and serving path for traffic through those locations rather than the API you'd ping to check Fastly's health. A regional POP problem like this can degrade real traffic for users near those edges while every synthetic check elsewhere stays green, because the check and the affected path simply don't overlap. This is the general shape to watch for with any CDN: the edge that's broken is rarely the edge your monitoring happens to sit near. Your own uptime checks tell you whether your origin and application are healthy, but they can't tell you whether the CDN serving your traffic is degraded in a region you don't probe. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

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.