Outage in Salesforce
Service Disruption
Resolved Major
Need to monitor Salesforce outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Salesforce, and never miss an outage again.
Start Free Trial
Outage Details
Components affected
Salesforce AP43 Salesforce AP44 Salesforce AP45 Salesforce AP46 Salesforce AP47 Salesforce AP48 Salesforce AP49 Salesforce AP50 Salesforce CS236 Salesforce CS237 Salesforce CS238 Salesforce CS239 Salesforce CS240 Salesforce CS241 Salesforce CS242 Salesforce CS243 Salesforce CS244 Salesforce CS245 Salesforce CS246 Salesforce CS247 Salesforce CS248 Salesforce CS249 Salesforce CS250 Salesforce CS251 Salesforce CS252 Salesforce CS253 Salesforce CS254 Salesforce CS255 Salesforce CS256 Salesforce CS257 Salesforce CS258 Salesforce CS259 Salesforce CS260 Salesforce CS261 Salesforce CS262 Salesforce CS263 Salesforce CS264 Salesforce CS265 Salesforce CS266 Salesforce CS267 Salesforce CS268 Salesforce CS269 Salesforce CS270 Salesforce CS271 Salesforce CS272 Salesforce CS273 Salesforce CS274 Salesforce CS275 Salesforce CS276 Salesforce CS277 Salesforce CS278 Salesforce CS279 Salesforce CS280 Salesforce CS281 Salesforce CS282 Salesforce CS283 Salesforce CS290 Salesforce CS291 Salesforce CS293 Salesforce CS294 Salesforce CS295 Salesforce CS310 Salesforce CS311 Salesforce CS312 Salesforce CS313 Salesforce CS314 Salesforce CS315 Salesforce CS321 Salesforce CS341 Salesforce CS342 Salesforce CS343 Salesforce CS344 Salesforce NA223 Salesforce NA224 Salesforce NA225 Salesforce NA226 Salesforce NA231 Salesforce NA232 Salesforce NA233 Salesforce NA234 Salesforce NA235 Salesforce NA236 Salesforce NA237 Salesforce NA238 Salesforce NA239 Salesforce NA240 Salesforce NA241 Salesforce NA242 Salesforce NA243 Salesforce NA244 Salesforce NA245 Salesforce NA246 Salesforce NA247 Salesforce NA248 Salesforce NA249 Salesforce NA251 Salesforce NA252 Salesforce NA253Latest Updates ( sorted recent to last )
The team has rolled back all production instances and is conducting final checks. The team is now focusing on the sandbox environment in groups, which they expect to take considerable time.
We will provide another update in 60 minutes or sooner if new information becomes available.
The rollback is confirmed to successfully resolve the issue and the team will continue to implement the rollback across the remaining instances. The team has developed a script to perform this rollback on the impacted instances in groups to speed up the resolution.
We will provide another update in 60 minutes or sooner if new information becomes available.
The team continues to see positive results following the completion of the rollback on a number of instances. The rollback is being done in a staggered manner due to the scale of the issue. As rollbacks complete, affected customers should begin to see improved performance. The rollback efforts are expected to take several hours.
We will provide another update in 90 minutes or sooner if new information becomes available.
The team successfully rolled back the change on a sandbox instance, where they observed improved database connectivity performance. The team is in the process of rolling back the change on a small number of production instances and will analyze the results.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
The team is performing a rollback on a test instance to verify whether the application can establish a stable connection to the database.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
The database team has analyzed affected databases and identified some inconsistencies. The databases are now being restored from the most recent stable backup. The Network team has identified and applied a rate limit to regulate and optimize connections. Further investigations have highlighted a recent change as a potential trigger, and as of 09:00 UTC, teams are working to validate a rollback of this in a canary instance in parallel.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
At 05:55 UTC on November 15, 2024, the Salesforce Technology team became aware of a service disruption impacting instances across multiple Data Centers. At approximately 08:15 UTC, teams began taking steps to control excessive traffic, network utilization, and database stability to mitigate the impact quickly. We don’t yet understand when customers may begin experiencing improvement as a result of these actions.
Initially, this was posted as an Informational Message due to the widespread impact, but as instances were identified, we have moved to post updates here against impacted instances. Previous posts related to this issue can be found at https://status.salesforce.com/generalmessages/1476
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Users report inability to log into Salesforce, encountering errors like 'bad error', server error 400, and maintenance messages. Service appears down.
Latest Salesforce outages
Start monitoring all your vendors in just 5 minutes
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 3276 services available
Integrations with
Setup in 5 minutes or less
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime