Salesforce favicon

Salesforce outage on 2026-10-19

salesforce.com
October 2026 19 Minor incident

Salesforce had three separate incidents on 19 October 2026, the longest a 12h 35m Data Cloud disruption caused by a third-party provider on Salesforce's own side of the chain. If your product depends on Data 360, Calculated Insights, Data Transform or related ingestion jobs, this was a Salesforce-side fault, not yours.

Started

01:45 UTC

Duration

Lasted 4h 10m

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, BRA16, BRA18, BRA24, BRA28, BRA32, BRA34, BRA36, BRA38, BRA48, BRA50, CAN28, CAN36, CAN42, CAN44, CAN46, CAN52, CAN56, NA235, NA241, NA242, NA243, NA253, SGP10, USA1, USA234, USA236, USA250S, USA252S, USA272, USA290, USA302, USA312, USA314, USA316, USA320, USA322, USA328, USA330, USA332, USA334, USA336, USA338, USA34, USA340, USA346, USA348, USA350, USA352, USA356, USA36, USA360, USA366S, USA372, USA374, USA376, USA3S, USA412, USA424, USA468, USA472, USA474, USA564, USA574, USA576, USA578, USA586, USA588, USA590, USA592, USA600, USA60S, USA612, USA614, USA616, USA618, USA620, USA622, USA632, USA638, USA648, USA680, USA716, USA718, USA720, USA724, USA728, USA730, USA732, USA740, USA744, USA746, USA752S, USA760S, USA764S, USA778, USA780, USA810, USA842, USA862, USA864, USA866, USA868, USA220, USA240S, USA242S, USA244S, USA248S, USA254S, USA256S, USA258S, USA260S, USA2S, USA318, USA324, USA326, USA342, USA344, USA354, USA358, USA384, USA80S, USA856, USA870S, USA872S, USA874S, USA876, USA644, USA748, USA674

What happened?

Salesforce logged three incidents on 19 October 2026, starting with an Order Management Feature Degradation at 01:45 that ran 4h 10m, and ending with a Feature Disruption starting at 20:24 that ran 1h 18m and carries no further updates. The bulk of the day's impact sat in the middle incident, a Data Cloud Feature Degradation that began at 12:31 and ran 12h 35m, Salesforce's longest filing of the day. Salesforce's own updates say Data 360 activation jobs were queued and timing out, with Marketing Cloud Connector, Calculated Insights, Data Transform and data ingestion jobs also affected. Salesforce attributed the trigger to a third-party provider issue, and spent the afternoon testing a switch to alternative infrastructure while that provider worked on a rollback. Two separate impactRadiusIncrease updates, at 16:12 and 20:25, show Salesforce expanding the list of affected instances as the day went on, eventually touching 12 components including USA1, USA2S, USA3S, SGP10, CAN28, USA34, USA36, USA60S, BRA14, BRA16, BRA18 and CAN36, out of 130 components Salesforce tracks. By 17:36 Salesforce said most affected services were processing new jobs again, but older queued jobs kept failing as the third-party fix deployed, and Salesforce warned customers that some of those jobs would need to be rerun manually. The last update on this incident, at 23:43, still described a backlog that was "decreasing steadily" but not yet cleared. No user reports were filed during the window on any of the three incidents. No post-mortem has been published for any of them, and Salesforce's status page does not name the third-party provider involved.

Learning

The record here shows a failure sitting inside Salesforce's own processing pipeline, specifically a third-party dependency behind Data Cloud, not in anything exposed at your application's edge. Pinging your own endpoints would not have caught this: your product would keep responding normally while jobs queued and timed out upstream, because the fault was in asynchronous job processing, not in request handling. That is exactly the kind of outage where your own uptime checks stay green and the provider's status page tells a different story, and both readings are correct at once. Salesforce's own 90 day history shows 108 incidents with a median duration of 2 hours 28 minutes, so a 12h 35m incident sits well outside what you'd expect from a typical Salesforce disruption. If activation jobs, Calculated Insights or Data Transform outputs look stale or missing in your product, check Salesforce's status history before assuming your own integration broke. 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.