Salesforce favicon

Salesforce outage on 2026-11-12

salesforce.com
November 2026 12 Minor incident

Salesforce logged four separate incidents on 12 November 2026, two of them running for hours before resolution and one still open. The faults sat inside Salesforce's own release and configuration pipeline, not in anything on your end.

Started

12:31 UTC

Duration

Lasted 4h 5m

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: GBR74, GBR76, GBR78, GBR80, GBR82, GBR84, GBR86, GBR88, GBR90S, GBR92S, GBR94, GBR96, GBR98, USA202S, USA20S, USA224S, USA226, USA228, USA22S, USA230, USA232, USA234, USA236, USA238, USA26, USA262S, USA268S, USA270S, USA272, USA274, USA276, USA278, USA280, USA282, USA286, USA288, USA28S, USA290, USA292, USA294, USA296, USA300, USA302, USA304, USA30S, USA32S, USA34, USA36, USA364, USA408, USA410, USA412, USA414, USA416, USA418, USA420, USA422, USA424, USA426, USA428, USA430, USA432S, USA434S, USA436, USA438, USA440, USA442, USA444, USA446S, USA448S, USA450, USA452, USA454, USA456, USA460, USA462, USA464, USA466, USA468, USA470, AUS102, AUS14S, AUS16S, AUS18S, AUS20S, AUS22S, AUS24S, AUS26S, AUS28S, AUS2S, AUS36S, AUS38S, AUS4S, AUS58, AUS60, AUS62, AUS64, AUS66, AUS68, AUS6S, AUS70, AUS72, AUS74, AUS76, AUS78, AUS80S, AUS82, AUS84, AUS86, AUS88, AUS90, AUS92, AUS94, DEU100, DEU102, DEU104S, DEU106, DEU108, DEU10S, DEU110, DEU112, DEU114S, DEU116S, DEU118, DEU120, DEU122, DEU124, DEU126, DEU128, DEU12S, DEU14S, DEU16S, DEU20S, DEU2S, DEU36, DEU38, DEU4S, DEU52, DEU54, DEU56, DEU58, DEU60, DEU62S, DEU66, DEU68, DEU6S, DEU70, DEU72, DEU74, DEU76, DEU78, DEU84, DEU86, DEU8S, DEU90, DEU92, DEU94, DEU96, FRA100, FRA104, FRA12S, FRA24S, FRA2S, FRA32, FRA34, FRA36, FRA42, FRA44, FRA46, FRA48, FRA4S, FRA50, FRA52, FRA54, FRA56, FRA62, FRA64, FRA66, FRA6S, FRA70, FRA74, FRA76, FRA78, FRA80, FRA84, FRA86, FRA88, FRA8S, FRA90, FRA96S, FRA98S, GBR100, GBR102, GBR106S, GBR108S, GBR110S, GBR112, GBR116, GBR118, GBR120, GBR122, GBR124, GBR2S, GBR34, GBR36, GBR38, GBR40S, GBR42S, GBR44S, GBR46, GBR48, GBR4S, GBR50, GBR52, GBR54, GBR56, GBR58, GBR60S, GBR62S, GBR64, GBR66, GBR68, GBR70, GBR72, USA472, USA474, USA476, USA478, USA480, USA488S, USA490S, USA494, USA496, USA534S, USA538, USA540S, USA542S, USA544, USA546, USA548, USA550, USA552, USA554, USA556, USA558, USA560, USA562, USA564, USA566, USA568, USA570, USA572, USA574, USA576, USA578, USA580, USA582, USA584, USA586, USA588, USA590, USA592, USA594, USA596, USA598, USA600, USA602, USA604, USA606, USA608, USA60S, USA610, USA612, USA614, USA616, USA618, USA620, USA622, USA624, USA626, USA628, USA62S, USA630, USA632, USA634, USA636, USA638, USA640, USA642, USA644, USA646, USA648, USA650, USA652, USA654S, USA656S, USA658S, USA660S, USA662S, USA664S, USA666S, USA668S, USA670S, USA672S, USA674, USA676, USA678, USA680, USA682, USA684, USA686, USA688, USA690, USA692, USA694, USA696, USA698, USA700, USA702, USA704, USA706, USA708, USA880S, USA882S, USA884S, USA886S, USA888S, USA890S, USA892S, USA894S, USA896S, USA898S, USA8S, USA900S, USA902S, ARE2S, ARE4S, BRA2S, BRA4S, BRA54S, BRA6S, BRA8S, CAN20S, CAN2S, CAN4S, CAN6S, CAN70S, CAN86S, CAN8S, CHE26S, CHE2S, CHE4S, CS236, CS237, CS238, CS239, CS240, CS241, CS242, CS243, CS244, CS245, CS246, CS247, CS248, CS250, CS251, CS252, CS253, CS254, CS255, CS256, CS257, CS258, CS259, CS260, CS261, CS262, CS263, CS264, CS265, CS266, CS267, CS268, CS269, CS270, CS271, CS272, CS273, CS275, CS276, CS277, CS283, ISR2S, ISR4S, ITA22S, ITA2S, ITA32S, ITA4S, SGP2S, SWE120S, SWE28S, SWE2S, SWE30S, SWE44S, SWE4S, SWE60S, SWE6S, SWE88S, SWE90S, SWE92S, SWE94S, SWE96S, USA240S, USA242S, USA244S, USA248S, USA250S, USA252S, USA254S, USA256S, USA258S, USA260S, USA2S, USA366S, USA3S, USA710S, USA712S, USA750S, USA752S, USA754S, USA756S, USA758S, USA760S, USA762S, USA764S, USA766S, USA768S, USA770S, USA772S, USA774S, USA786S, USA792S, USA804S, USA80S, USA836S, USA870S, USA872S, USA874S, USA916S

What happened?

The day's first incident started at 12:31 UTC and ran for 4 hours 5 minutes. It affected the Field Service Lightning Dispatch and Scheduling Console in sandbox environments, where customers could not view or use their custom actions, blocking some sandbox deployments. Salesforce traced it to a recent release, paused the rollout, and rolled the release back instance by instance, with one instance still lagging behind the rest by the last update at 16:16 UTC. A second incident began at 13:16 UTC and lasted 4 hours 57 minutes, hitting Agentforce connections through the mobile SDK and the Life Sciences iPad application. Salesforce's own updates show this one was messier than first thought: the errors actually began on 11 November at 03:00 UTC, well before the release Salesforce initially suspected, and the eventual cause was a configuration change that had stopped passing a required identifier to Agentforce. A third incident, labelled a Spiff Feature Disruption, opened at 19:24 UTC and closed after 1 hour 25 minutes, with Salesforce saying only that it had identified a "potential cause" without naming it. A fourth filing, a security advisory concerning ComplianceQuest Connected Applications, opened at 21:56 UTC with no further updates and remains open. Across all four, Salesforce published 20 updates and no user reports were filed during the window. Of the 451 components Salesforce tracks, a dozen named ones, spanning ARE, BRA and CAN instance groups, appear in these incident records.

Learning

Every fault on this page lived inside Salesforce's release and configuration process, in places an external check on your own product would never touch. A sandbox console losing custom actions, a mobile SDK losing a session identifier, a feature disruption with an unnamed cause: none of these show up as a dropped connection from the outside, because the platform itself stayed reachable while specific features inside it broke. That is the general shape to watch for with Salesforce: your product can look fine from outside while a dependency on an internal Salesforce feature quietly fails. Salesforce's 90 day history shows 128 incidents with a median duration of 2 hours 4 minutes, so this kind of partial, feature-level failure is routine rather than rare. Watching your own endpoints only tells you your half is up. UptimeRobot now watches Salesforce's side as well, 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.