Linode's Block Storage service in its BR-GRU (São Paulo) data centre broke starting at 20:17 UTC on 28 October 2026. If your product creates, deletes or clones storage volumes in that region, those calls could fail. Linode says the problem was on its end.
Started
20:17 UTC
Duration
Not closed by vendor
Source
IsDown
Next time
Linode 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.
What happened?
Linode opened the incident at 20:17 UTC, naming the fault as a "Service Issue" affecting Block Storage in BR-GRU, its São Paulo data centre. The update is specific about the symptom: volume creation, deletion and cloning may fail during the window. One minute later, at 20:18 UTC, Linode posted that a fix had been implemented and that it was monitoring the results. That is the entire public record for this incident, two updates a minute apart. No components list was published alongside this, so there is nothing further to check for scope beyond what Linode wrote in those two lines. No user reports were filed in this window to corroborate or add colour to Linode's account. The incident carries no resolved status as of the last update, and the day's overall duration is marked ongoing, so treat "monitoring the results" as Linode's current, not final, word. For context, Linode logged 24 incidents in the past 90 days with a median duration of 6 hours 31 minutes, and across its history it averages 7.7 incidents a month, so a short-duration storage fault in a single region is a familiar shape for this provider. Whether the fix fully held is not something Linode has confirmed yet, only that it believes it has.
Learning
This incident sits specifically in Block Storage, a backend layer that your own uptime checks on your application endpoints would not necessarily catch, because a failed volume clone or creation call inside Linode's infrastructure does not always surface as a visible error to every user immediately. That is the layer worth remembering: storage provisioning can break while your front end keeps answering requests normally, at least for a while. UptimeRobot's own 30-day figures for Linode show 12 incidents with only 8 resolved and a median duration of 15h 13m, a gap between "monitoring" and "resolved" that is worth sitting with before you assume a quick fix note means the issue is over. Linode's own history of 24 incidents in 90 days with a median duration over six hours suggests these things don't always close as fast as the first update implies. If your product relies on Linode's Block Storage in São Paulo, a clean status page on your own monitoring doesn't tell you whether volume operations are succeeding underneath. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.