Salesforce favicon

Salesforce outage on 2026-10-29

salesforce.com
October 2026 29 Major incident

Salesforce logged four separate incidents on 29 October, touching Commerce Cloud On-Demand Sandboxes and GovCloud infrastructure across seven components. The longest ran 17h 18m on GovCloud performance, and the cause named by Salesforce for the sandbox disruption was an expired certificate on their own side.

Started

10:56 UTC

Duration

Lasted 1h 42m

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: USA9404S, USA9406S, ODS-AP01, ODS-EU01, ODS-US01, ODS-US03, JPN6S

What happened?

Salesforce's status history shows four incidents starting between 06:08 and 21:08 UTC on 29 October. The first was a Performance Degradation lasting 58 minutes with no further detail published. Two more incidents, both titled "On Demand Sandbox Service Disruption," started at the same time, 10:56 UTC, one running 1h 42m and the other 23m, affecting Commerce Cloud On-Demand Sandboxes in all regions. For the longer of the two, Salesforce posted four updates. They said affected sandboxes were stuck in a "Starting" state and customers could not access or restart them, and identified an expired certificate as the cause. The updates track a slow fix: a new certificate was created, its automated approval was rejected due to a missing configuration, it was manually approved, then staged through a test environment before production, with each stage expected to take about 30 minutes. The fourth incident, starting at 21:08 UTC, is titled "GovCloud performance degradation, Third-party Infrastructure Provider issue, Initial" and ran 17h 18m, the longest of the day, but carries no updates explaining what the third-party provider issue actually was. Seven components appear across the day's incidents: JPN6S, ODS-US01, ODS-US03, ODS-AP01, ODS-EU01, USA9404S and USA9406S. No user reports were filed during this window. Over the preceding 90 days Salesforce logged 117 incidents with a median duration of 2 hours 14 minutes, so a day with four incidents and one running past 17 hours sits outside the typical pattern.

Learning

This day shows a failure inside Salesforce's own sandbox provisioning and GovCloud infrastructure, not something that shows up by pinging your own application. An expired certificate on Salesforce's side left sandboxes stuck in a starting state regardless of how your product called them, and a third-party infrastructure issue sat behind the GovCloud slowdown for over 17 hours with no breakdown of what broke. Watching your own endpoints only tells you that your calls to Salesforce are failing, not why, and not whether the fault sits with certificate renewal, approval automation, or an upstream infrastructure provider you have no visibility into. Over the last 30 days, external monitoring across Salesforce recorded 41 incidents with a median duration of 1h 23m, a useful baseline for how often this provider's side breaks independent of what your own checks show. 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.