Salesforce favicon

Salesforce outage on 2026-10-27

salesforce.com
October 2026 27 Major incident

Salesforce logged two separate incidents on 27 October, the second a login and access failure that ran 5h 1m and traced back to a network configuration change. The fault sat on Salesforce's side, affecting the DEU90 instance and others added later in the day.

Started

21:41 UTC

Duration

Lasted 5h 1m

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: DEU90

What happened?

The day started with a short "Performance Degradation" incident at 17:37, lasting 13 minutes, with a single update saying Salesforce was investigating the cause and would follow up in 30 minutes. No further detail was published on that one, and it closed without a stated cause. The second incident is the one that matters. It started at 21:41, though Salesforce's own update says the impact began earlier, around 20:59 UTC, with customers on affected instances unable to log in or access their services. Salesforce first said it was engaging third-party partners, then at 22:00 ruled out a third-party disruption and pivoted to looking at recent changes. By 22:10 it had started reverting a recent change as a precaution, and spent the next several updates, at 22:25, 22:46 and 22:59, still working through that rollback while also checking network infrastructure and other recent changes in parallel. At 01:09 Salesforce reported it had completed a rollback of the network configuration change in a lower environment, with validation steps still pending before pushing to production. At 01:38 it issued an "impactRadiusIncrease" update, confirming the problem affected more instances than first reported, with DEU90 named among them and further instances to receive direct communication. The incident closed at 5h 1m total duration. No user reports were filed in this window, and components_affected lists only DEU90, though Salesforce's own text makes clear other instances were also hit. No post-mortem has been published explaining the root cause of the network configuration change itself.

Learning

This incident is a clean example of a failure that sits entirely on the provider's side: logins and service access failing because of a network configuration change deep in Salesforce's infrastructure, not because of anything in your own integration or code. There is no our_probes data on this record, which means an external check against your own endpoints would tell you nothing about this kind of fault, since the problem never touched your side of the connection at all. Salesforce's own timeline shows it took hours to even identify the change, revert it in a lower environment, and validate before production, which is a normal shape for infrastructure-level incidents: slow to diagnose, slower to safely undo. Over the last 90 days Salesforce has logged 113 incidents with a median duration of 2 hours 23 minutes, so a multi-hour outage like this one is not unusual for this provider. If your own monitoring only watches your application layer, an incident like this can pass unnoticed until support tickets start arriving. 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.