Fastly's On-the-Fly Packaging component returned 503 errors for 52 minutes on 26 October 2026. The fault sat inside Fastly's video packaging pipeline, not in anything you control.
Started
18:24 UTC
Duration
Lasted 52m
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: On-the-fly Packager, Streaming
What happened?
Fastly opened an incident at 18:24 UTC titled "Content Delivery (CDN) with Possible Impact", covering the Streaming and On-the-Fly Packager components. The first update said customers using On-the-Fly Packaging (OTFP) were seeing 503 errors and that engineers were working to diagnose the contributing factor. By 18:51 Fastly said it believed it had identified the contributing factor and was developing a fix, and added that all other products and services were unaffected. At 19:05 Fastly posted that the fix had been deployed, that OTFP had recovered, and that error rates and latency had returned to nominal levels, with the team continuing to monitor before resolving the incident formally. That is the last update on record, filed 52 minutes after the incident opened. No post-mortem has been published explaining what the contributing factor actually was, so the specific cause is not on the record beyond "a contributing factor" that Fastly says it fixed. No user reports were filed during the window on this page. Fastly's own 90 day history shows 17 incidents with a median duration of 7 hours 2 minutes, so a 52 minute incident sits well below the usual length for this provider. Across all time Fastly has logged 1,006 incidents at a rate of roughly 13.1 per month, which is the backdrop against which a single 52 minute OTFP incident should be read.
Learning
UptimeRobot's own probes for Fastly's api-control component in the EU and NA regions held 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was not registered against those probes. That is not a contradiction. The probes watch Fastly's control plane API, while the outage itself sat inside On-the-Fly Packaging, a separate video delivery component that general API checks do not exercise. This is the common shape of a CDN provider issue: one specific product path fails while the rest of the platform, including the parts your synthetic checks happen to hit, stays green. If your own product depends on Fastly's OTFP for streaming and you were only watching your own endpoints, you would have seen errors on your side with nothing in your own infrastructure to explain them. Watching your own endpoints tells you something broke, it does not tell you whether the fault is yours or the provider's. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.