Salesforce logged four separate incidents on 30 October 2026, the longest a 9h 29m disruption tied to file storage connectivity. The root cause sat inside Salesforce's own network routing, not in anything you control.
Started
21:14 UTC
Duration
Lasted 9h 29m
Source
IsDown
Next time
Salesforce 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: BRA14, BRA24, BRA36, BRA48, BRA50, USA346, USA3S, USA564, USA638, USA648, USA720, GBR64, USA1, USA220, USA240S, USA242S, USA244S, USA248S, USA250S, USA252S, USA254S, USA256S, USA258S, USA260S, USA2S, USA312, USA314, USA316, USA318, USA320, USA322, USA324, USA326, USA328, USA330, USA332, USA334, USA336, USA338, USA340, USA342, USA344, USA348, USA350, USA352, USA354, USA356, USA358, USA360, USA366S, USA372, USA374, USA376, USA384, USA80S, USA856, USA870S, USA872S, USA874S, USA876, DEU96, DEU54, ITA10, ITA38, SWE10, GBR46, DB6001, DB6002, DB6003, DB6004, DB6005, DB6006, DB6007, DB6008, DB6009, DB601, DB6010, DB6011, DB6012, DB6013, DB6014, DB6015, DB6016, DB6018, DB6019, DB602, DB6020, DB6021, DB6027, DB6028, DB6029, DB603, DB6030, DB6031, DB6032, DB605, DB607, DB608, DB613, DB615, DB616, DB617, DB618, DB621, DB623, DB625, DB626, DB627, DB628, DB631, DB632, DB633, DB634, DB636, DB637, DB638, DB639, DB640, DB641, DB645, DB646, DB647, DB648, DB649, DB651, DB652, DB653, DB654, DB655, DB656, DB658, DB659, DB660, DB661, DB662, DB663, DB664, DB665, DB667, DB668, DB669, DB670, DB671, DB672, DB673, DB674, DB676, DB677, DB678, DB680, DB681, DB682, DB684, DB686, DB688, DB689, DB690, DB691, DB692, DB693, DB694, DB695, DB696, DB697, DB698, DB7
What happened?
Salesforce's status page recorded four incidents through the day, starting with a 6 minute Marketing Cloud Engagement degradation at 14:16, followed by a 1h 10m Agentforce feature degradation at 17:33, a 9 minute feature disruption at 22:13, and the longest of the day, a Service Disruption starting at 21:14 that ran for 9h 29m. That last incident touched 166 components in total, including DB6012, DB605, DB621, DB6009, DB647, DB672, DB7, DB6013, DB601, DB625, DB6015 and DB616. Salesforce's updates describe connectivity failures between some Salesforce environments and Long-Term File Storage, with delays or intermittent failures accessing files and org migrations affected. By 21:54 engineering had traced it to a recently added traffic-routing path whose requests were timing out, and planned migrations on the affected instance were paused as a precaution. The 22:22 update named the actual fault: required network permissions had not been put in place before traffic was enabled on that new proxy path. It also noted the cloud management console itself had become unavailable, forcing Salesforce to engage its cloud provider just to get back into the systems needed to fix the original problem. By 22:58 a routing change had been tested successfully and teams were working to apply it in production, alongside a separate sign-in issue blocking internal access to that same console. No further update is on record after that, and the incident's listed duration of 9h 29m indicates it was eventually resolved. No post-mortem has been published, and no user reports were filed during the window for any of the four incidents.
Learning
This was a routing and permissions fault inside Salesforce's own infrastructure, not something that would show up by pinging your own endpoints. Salesforce's engineers themselves needed to get into a cloud management console to fix it, and even that console went down partway through, which tells you how deep inside the provider's stack the failure sat. Watching your own application from your own side tells you your code and your integrations are fine, but it says nothing about whether Salesforce's internal network paths between its environments and its file storage are healthy. The two readings don't conflict, they are just looking at different halves of the same connection. Over the past 90 days Salesforce has logged 120 incidents with a median duration of 2 hours 14 minutes, so a long outage like this one is 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.
