Fastly Object Storage in the EU-Central region had intermittent upload failures for 15 hours and 19 minutes starting at 23:00 UTC. The fault sat inside Fastly's storage service, not in your own stack.
Started
23:00 UTC
Duration
Lasted 15h 19m
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: Object Storage
What happened?
Fastly opened the incident at 23:00 UTC, reporting intermittent failures when uploading objects to Object Storage in the EU-Central region. The first update said engineers were working to diagnose the contributing factor and promised another update within the hour. That next substantive update did not land until 07:55 UTC, nearly nine hours later, when Fastly said it believed it had identified the contributing factor and was developing a fix. That same update stated all other products and services remained unaffected, so the scope stayed confined to this one component in one region. A third update at 13:45 UTC said engineering had confirmed the impact was mitigated, with the team continuing to monitor for stability before resolving the incident formally. In total, three updates cover the full 15h 19m window, which is a thin record for an outage of that length. No user reports were filed during the window on this page. Fastly has not published a post-mortem explaining what the contributing factor actually was, only that one was identified. Over the past 90 days Fastly has logged 16 incidents with a median duration of 9 hours 47 minutes, so this one ran noticeably longer than typical. Across all time, Fastly has recorded 1,003 incidents at a pace of roughly 13 per month, which puts this single-region storage issue inside a pattern of frequent, usually short-lived incidents rather than a one-off.
Learning
UptimeRobot's own probes against Fastly's api-control component in the EU and NA regions showed 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was not registered against that check. That is not a contradiction. The fault was specific to object uploads in EU-Central Object Storage, a different layer entirely from the control API path those probes exercise, so a clean probe result and a real, hours-long upload failure can both be true at once. This is the general shape of a storage-layer outage: the control plane answers normally, authentication and routing look fine, but writes to a specific storage backend in a specific region quietly fail or stall. If your product uploads files to Fastly Object Storage from EU-Central, watching your own endpoints would only tell you that your service is up, not that writes into Fastly's storage are failing underneath you. Across UptimeRobot's own 30 day stats, Fastly has had 7 incidents, all resolved, with a median duration of 10h 6m, so slow-to-resolve storage issues are not unusual for this provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
