Outage in Salesforce
Feature Disruption
Resolved Minor
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 ARE2S Salesforce AUS14S Salesforce AUS18S Salesforce AUS20S Salesforce AUS22S Salesforce AUS26S Salesforce AUS2S Salesforce AUS36S Salesforce AUS38S Salesforce BRA30 Salesforce BRA54S Salesforce BRA6S Salesforce CAN38 Salesforce CAN42 Salesforce CAN70S Salesforce CAN86S Salesforce CHE16 Salesforce CHE2S Salesforce CS133 Salesforce CS234 Salesforce CS291 Salesforce CS293 Salesforce CS294 Salesforce CS295 Salesforce CS308 Salesforce CS311 Salesforce CS312 Salesforce CS313 Salesforce CS314 Salesforce CS321 Salesforce CS384 Salesforce DEU100 Salesforce DEU118 Salesforce DEU122 Salesforce DEU128 Salesforce DEU38 Salesforce DEU48S Salesforce DEU54 Salesforce DEU62S Salesforce DEU6S Salesforce DEU72 Salesforce DEU78 Salesforce DEU94 Salesforce FRA24S Salesforce FRA34 Salesforce FRA48 Salesforce FRA56 Salesforce FRA80 Salesforce FRA90 Salesforce GBR100 Salesforce GBR102 Salesforce GBR108S Salesforce GBR34 Salesforce AUS24S Salesforce BRA2S Salesforce CAN2S Salesforce CAN6S Salesforce CHE26S Salesforce DEU114S Salesforce DEU116S Salesforce DEU12S Salesforce DEU14S Salesforce DEU16S Salesforce DEU20S Salesforce DEU2S Salesforce FRA12S Salesforce FRA2S Salesforce FRA6S Salesforce FRA96S Salesforce GBR106S Salesforce GBR110S Salesforce GBR2S Salesforce GBR42S Salesforce GBR44S Salesforce GBR92S Salesforce ITA22S Salesforce SWE2S Salesforce SWE2S Salesforce SWE30S Salesforce SWE60S Salesforce SWE6S Salesforce SWE88S Salesforce SWE90S Salesforce SWE92S Salesforce USA20S Salesforce USA224S Salesforce USA244S Salesforce USA252S Salesforce USA254S Salesforce USA258S Salesforce USA262S Salesforce USA268S Salesforce USA270S Salesforce USA28S Salesforce USA30S Salesforce USA32S Salesforce USA3S Salesforce USA540S Salesforce USA542S Salesforce USA654S Salesforce USA658S Salesforce USA660S Salesforce USA662S Salesforce USA666S Salesforce USA668S Salesforce USA670S Salesforce USA672S Salesforce USA764S Salesforce USA770S Salesforce USA870S Salesforce USA872S Salesforce GBR50 Salesforce GBR54 Salesforce GBR70 Salesforce GBR72 Salesforce GBR86 Salesforce GBR88 Salesforce GBR90S Salesforce GBR98 Salesforce IND10S Salesforce IND12S Salesforce IND20S Salesforce IND22S Salesforce IND24S Salesforce IND2S Salesforce IND3S Salesforce IND4S Salesforce IND54S Salesforce IND6S Salesforce IND8S Salesforce ISR4S Salesforce ITA28 Salesforce ITA2S Salesforce ITA30 Salesforce ITA8 Salesforce JPN10S Salesforce JPN12S Salesforce JPN18S Salesforce JPN20S Salesforce JPN22S Salesforce JPN28S Salesforce JPN2S Salesforce JPN6S Salesforce KOR2S Salesforce NA164 Salesforce NA165 Salesforce NA211 Salesforce NA226 Salesforce NA231 Salesforce NA238 Salesforce NA253 Salesforce SGP2S Salesforce SGP6S Salesforce SWE10 Salesforce SWE100 Salesforce SWE26 Salesforce SWE46 Salesforce SWE56 Salesforce SWE58 Salesforce SWE64 Salesforce SWE8 Salesforce SWE82 Salesforce SWE84 Salesforce SWE94S Salesforce SWE96S Salesforce USA220 Salesforce USA222S Salesforce USA236 Salesforce USA240S Salesforce USA246S Salesforce USA250S Salesforce USA256S Salesforce USA26 Salesforce USA260S Salesforce USA316 Salesforce USA318 Salesforce USA322 Salesforce USA354 Salesforce USA410 Salesforce USA442 Salesforce USA448S Salesforce USA534S Salesforce USA568 Salesforce USA610 Salesforce USA616 Salesforce USA618 Salesforce USA632 Salesforce USA638 Salesforce USA656S Salesforce USA664S Salesforce USA710S Salesforce USA752S Salesforce USA754S Salesforce USA756S Salesforce USA760S Salesforce USA762S Salesforce USA766S Salesforce USA768S Salesforce USA772S Salesforce USA774S Salesforce USA80S Salesforce USA8SLatest Updates ( sorted recent to last )
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
The Salesforce Technology team has thoroughly validated the fix, confirming its positive results and optimal performance in resolving the issue. To ensure a seamless rollout, the team will deploy the fix in a staggered manner across all impacted instances, which may require additional time for full completion.
We will provide an update once the deployment is successfully completed or if any additional information becomes available.
As of 02:25 UTC, on February 10, 2025: The Salesforce Technology team now better understands the trigger and has identified complications with an earlier release rollback as the trigger for this issue. The fix release has been validated in a sandbox environment and is being rolled out to a small number of instances where performance will be monitored. This may take between 60-90 minutes. Once performance can be validated, the fix will be rolled out across all impacted instances.
We’ll provide an update once new information becomes available.
At 00:50 UTC, on February 10, 2025: The Salesforce Technology team continues to validate the performance of the fix release. Deployment logistics are being planned, should the fix release validation be successful. Additional resolution paths also continue to be investigated, as well as further investigation into the root cause of the issue.
We’ll provide an update once new information becomes available.
At 23:20 UTC, on February 9, 2025: The Salesforce Technology team has confirmed that Government Cloud (GovCloud) instances have not been impacted by this issue. These instances have now been removed from this Trust posting.
We’ll provide an update once new information becomes available.
At 23:00 UTC, on February 9, 2025: The Salesforce Technology team continues to investigate multiple resolution paths and believes the trigger for this issue is now understood. The primary action focuses on the development of a release that will address the issue and restore services to customers. This release is being finalized, then will undergo testing to validate performance. This will take approximately one hour to complete.
We’ll provide an update in 90 minutes, once release validation is clarified, or once new information becomes available.
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
We are working with multiple teams to determine whether a recent change was the trigger and whether reverting that change is the best path forward or whether a scheduled release will resolve the issue.
We’ll provide an update in 60 minutes or sooner if additional information becomes available.
There’s a feature disruption affecting customers across multiple instances that began at approximately 13:24 UTC on February 9, 2024. We became aware of the issue after customers began logging support cases.
Affected customers will receive an error when attempting to open the developer console and will not be able to open Apex classes. This will prevent them from working on any development, and they may also receive an internal server error.
Multiple teams are working on a path to resolution.
We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Latest Salesforce outages
Don't be the last to know when your dependencies go down
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 · 3746 services available
Integrations with
