Salesforce favicon

Salesforce outage on 2026-11-05

salesforce.com
November 2026 5 Minor incident

Salesforce's Marketing Cloud Engagement had a feature degradation lasting 8 minutes on 5 November 2026. The fault sat on Salesforce's side, across a cluster of database components tied to Marketing Cloud.

Started

14:41 UTC

Duration

Lasted 8m

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: DB10, DB10001, DB10006, DB10008, DB10010, DB10011, DB10012, DB10014, DB10015, DB10016, DB10017, DB10020, DB10021, DB10022, DB10024, DB10026, DB10028, DB10032, DB10033, DB10036, DB10039, DB10040, DB10044, DB10047, DB10048, DB10053, DB10056, DB10058, DB10063, DB10065, DB10066, DB10068, DB10070, DB10075, DB10076, DB10078, DB10079, DB10080, DB10081, DB10082, DB10085, DB10094, DB10097, DB10104, DB10117, DB10135, DB10136, DB10139, DB10141, DB10142, DB10147, DB10152, DB10178, DB10198, DB10207, DB10212, DB10218, DB10226, DB11001, DB11004, DB11021, DB11025, DB11033, DB11044, DB11049, DB11054, DB11057, DB11062, DB11066, DB11069, DB11093, DB11099, DB11126, DB11144, DB11147, DB11159, DB11162, DB11181, DB11233, DB11241, DB11244, DB11256, DB11271, DB11319, DB11373, DB11385, DB11418, DB11442, DB11451, DB11609, DB117, DB118, DB12006, DB12012, DB12015, DB12020, DB12026, DB12034, DB12038, DB12041, DB12058, DB12064, DB12074, DB12118, DB12123, DB12129, DB12130, DB12142, DB12160, DB12163, DB12166, DB12177, DB12184, DB12198, DB12201, DB12204, DB12219, DB12228, DB12249, DB12252, DB12253, DB12280, DB123, DB12307, DB12343, DB12379, DB12388, DB12406, DB12442, DB12451, DB12460, DB12601, DB13, DB13003, DB13033, DB13036, DB13060, DB13075, DB13084, DB13087, DB13099, DB131, DB13102, DB13108, DB13111, DB13114, DB13153, DB13156, DB13165, DB13171, DB13189, DB13192, DB13198, DB13201, DB13204, DB139, DB168, DB169, DB171, DB2, DB20, DB33, DB34, DB38, DB42, DB431, DB434, DB435, DB439, DB44, DB466, DB468, DB5, DB50109, DB51040, DB6007, DB6015, DB6027, DB603, DB6030, DB608, DB615, DB618, DB62, DB621, DB627, DB628, DB67, DB670, DB671, DB678, DB680, DB691, DB692, DB695, DB696, DB697, DB70, DB7007, DB7008, DB7015, DB7016, DB7022, DB7025, DB7026, DB7028, DB7030, DB7036, DB7037, DB7039, DB704, DB7044, DB7047, DB7049, DB7050, DB7052, DB7055, DB7059, DB7060, DB7067, DB7073, DB708, DB7082, DB709, DB7094, DB7099, DB710, DB7109, DB7125, DB7131, DB7144, DB715, DB7156, DB7159, DB716, DB7163, DB7164, DB7165, DB7166, DB7168, DB7171, DB7176, DB7179, DB72, DB720, DB724, DB729, DB732, DB736, DB746, DB757, DB760, DB762, DB775, DB778, DB782, DB786, DB787, DB79, DB790, DB791, DB794, DB85, DB89, DB93, DB97

What happened?

Salesforce's status history logs one incident on this day, titled "Marketing Cloud Engagement Feature Degradation", starting at 14:41 UTC and running for 8 minutes. Twelve components are listed against it, including DB10, DB10001, DB10006 and nine others, all part of a set of 266 components Salesforce tracks across its platform. Salesforce published no updates during the incident, so there is no first-hand account of what the degradation looked like to someone using Marketing Cloud, or what fixed it. No user reports were filed during the window. Salesforce's own clock shows the incident opened and closed within the same 8 minutes, with nothing further added afterwards. That brevity and the lack of any update means the record cannot tell you whether the degradation affected sending, tracking, journeys or something else inside Marketing Cloud, only that Salesforce's own monitoring flagged a cluster of database components. Over the past 90 days Salesforce has logged 124 incidents with a median duration of 2 hours 6 minutes, so an 8 minute event sits well below the typical length of a Salesforce incident. Across all time Salesforce has recorded 2,506 incidents on this status page. No post-mortem has been published for this one.

Learning

This incident is a reminder that a status page entry with no further updates still counts as a real outage, even without detail on what broke for end users. Salesforce listed a dozen database components under the degradation, which points at the data layer behind Marketing Cloud rather than anything client side, so checking your own integration endpoints would not have caught it. If your own monitoring stayed quiet through this window while something inside Marketing Cloud misbehaved, that is expected: your monitoring watches your own systems, and Salesforce's internal database components sit outside that view entirely. UptimeRobot's 30 day data for Salesforce shows 48 incidents with 45 resolved and a median duration of 1h 38m, a different picture from the 8 minute event here, which shows how much incident length can vary even for the same provider. The lesson is to treat short, undocumented degradations like this one as evidence the fault lived on Salesforce's side, not yours. 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.