Salesforce favicon

Salesforce outage on 2026-10-26

salesforce.com
October 2026 26 Minor incident

Salesforce logged four separate incidents on 26 October 2026, running from a Marketing Cloud link-tracking fault just after 03:29 UTC through to a Tableau data source error that stayed open for 27h 26m. All four originated inside Salesforce's own infrastructure, affecting Marketing Cloud, Stack 7 email sending, and Tableau workbooks across a wide span of its AUS-numbered instances.

Started

03:29 UTC

Duration

Lasted 33m

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: DB47, DB7001, DB7002, DB7003, DB7004, DB7005, DB7006, DB7007, DB7008, DB7009, DB7010, DB7011, DB7012, DB7013, DB7014, DB7015, DB7016, DB7017, DB7018, DB7019, DB7020, DB7021, DB7022, DB7023, DB7025, DB7026, DB7027, DB7028, DB7029, DB703, DB7030, DB7031, DB7033, DB7034, DB7035, DB7036, DB7037, DB7038, DB7039, DB704, DB7040, DB7041, DB7042, DB7043, DB7044, DB7045, DB7046, DB7047, DB7048, DB7049, DB705, DB7050, DB7052, DB7053, DB7054, DB7055, DB7056, DB7058, DB7059, DB706, DB7060, DB7061, DB7062, DB7063, DB7064, DB7065, DB7066, DB7067, DB7068, DB7069, DB707, DB7070, DB7071, DB7073, DB7074, DB7075, DB7076, DB7077, DB7078, DB7079, DB708, DB7080, DB7081, DB7082, DB7083, DB7084, DB7085, DB7086, DB7087, DB7088, DB7089, DB709, DB7090, DB7091, DB7092, DB7093, DB7094, DB7095, DB7096, DB7097, DB7098, DB7099, DB710, DB7100, DB7101, DB7102, DB7103, DB7104, DB7105, DB7106, DB7107, DB7108, DB7109, DB711, DB7110, DB7111, DB7112, DB7113, DB7114, DB7115, DB7116, DB7117, DB7118, DB7119, DB712, DB7120, DB7121, DB7122, DB7123, DB7124, DB7125, DB7126, DB7127, DB7129, DB713, DB7130, DB7131, DB7132, DB7133, DB7134, DB7135, DB7137, DB7138, DB7139, DB714, DB7140, DB7141, DB7143, DB7144, DB7145, DB7146, DB7147, DB7148, DB7149, DB715, DB7150, DB7151, DB7152, DB7154, DB7155, DB7156, DB7158, DB7159, DB716, DB7160, DB7162, DB7163, DB7164, DB7165, DB7166, DB7167, DB7168, DB7169, DB717, DB7170, DB7171, DB7172, DB7173, DB7174, DB7175, DB7176, DB7177, DB7178, DB7179, DB718, DB719, DB720, DB721, DB724, DB725, DB727, DB728, DB729, DB730, DB731, DB732, DB733, DB734, DB735, DB736, DB737, DB738, DB739, DB740, DB741, DB742, DB743, DB744, DB745, DB746, DB747, DB748, DB749, DB750, DB752, DB753, DB754, DB755, DB756, DB757, DB758, DB759, DB760, DB762, DB763, DB764, DB765, DB766, DB767, DB770, DB771, DB772, DB773, DB774, DB775, DB776, DB777, DB778, DB779, DB780, DB781, DB782, DB784, DB785, DB786, DB787, DB788, DB790, DB791, DB792, DB793, DB794, DB795, DB797, DB798, DB799, ARE6, IND10S, IND116, IND122, IND28S, IND64, IND78, IND88, IND8S, 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

What happened?

The day opened at 03:29 UTC with a Feature Disruption on Marketing Cloud: affected customers got HTTP 400 errors and signature verification failures when clicking tracked email links, which meant the links never reached their intended destination URLs. Salesforce posted one update at 03:39 and closed that incident 33 minutes after it began. A second, undocumented Feature Disruption ran from 13:51 to 14:50, 25 minutes long, with no updates filed at all. The third incident, a Performance Degradation on Stack 7 starting 14:50, lasted 1h 17m and produced the most detailed account of the day: Salesforce traced it to exhausted storage capacity on the databases backing outbound email, expanded storage across two clusters in stages, and confirmed by 15:55 that email send volumes had returned to expected levels. Salesforce revised the incident's recorded start time twice during that window, saying impact began earlier than first identified, and noted that some send jobs entered an error state which it resumed on its own side without requiring customer action. The fourth and longest incident began at 16:48 UTC: Tableau workbooks threw an error when opening a data source, reading "that page could not be accessed. Either the data source does not exist or you do not have the necessary permissions." Salesforce published a workaround, bypassing the workbook's Data Sources list in favour of Explore then Data Sources by name, and linked a knowledge article. It took until 23:53 to confirm a root cause and say a fix was in the release process, and the incident itself ran 27 hours 26 minutes before resolving. Across all four incidents, the components list spans twelve AUS-numbered instances out of 298 tracked in total, and no user reports were filed in this window on Salesforce's own channels.

Learning

This record carries no our_probes entry, so there is no external monitoring read to compare against Salesforce's own account, but the shape of the day still tells you something useful. Three of the four incidents touched backend components, database storage, email send processing and Tableau's data source layer, that sit behind Salesforce's application surface and are invisible from outside unless you are specifically watching for the symptom, like HTTP 400s on tracked links or a broken Data Sources menu. A check that only confirms Salesforce's login page or API endpoint responds would have stayed green through all four incidents, because the fault was in specific features, not in Salesforce being reachable. The 25-minute Feature Disruption with zero updates is a reminder that Salesforce's own status page does not always explain what broke, only that something did. Salesforce's 90-day history shows a median incident duration of 2 hours 21 minutes, well under the 27h 26m this Tableau fault ran, so duration alone can mislead you about how bad a given day is. Your own monitoring covers your half of this relationship, whether your product calls Salesforce correctly, but UptimeRobot watching Salesforce's own infrastructure is what tells you, the next time something breaks, which side of the line it broke on.

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.