Salesforce Outage

At 09:00 UTC, on February 7, 2025, a service disruption began impacting customers. During this time customers are having difficulty accessing their Salesforce Core services and are seeing errors saying “An unexpected connection error occurred”. Additional teams have been engaged and are actively investigating. Some customers may already see signs of improvement.

This affects a small number of Veeva CRM customers. Feb 7, 1:00 AM PST - At 09:00 UTC, on February 7, 2025, a service disruption began impacting customers on pod DEU66. During this time customers are having difficulty accessing their Salesforce Core services and are seeing errors saying “An unexpected connection error occurred”. Additional teams have been engaged and are actively investigating.Feb 7, 1:27 AM PST - At 09:27 UTC, on February 07, 2025, the Salesforce Technology team became aware of a service disruption impacting a subset of customers. Affected customers may experience delays or unavailability in accessing their services. Initial investigations have shown resource constraints due to high network traffic utilizationMore pods are affected: BRA2S, BRA3, BRA4S, BRA5, BRA6S, BRA8S, BRA14, BRA16, BRA18, BRA24, BRA28, BRA30, BRA32, BRA34, BRA36, BRA38, BRA44, BRA48, BRA50, BRA54S, DEU66, DEU106, IDN2S, IDN4S, IDN6, IDN8, KOR1, KOR2S, KOR4S, KOR6, KOR8, SWE1, SWE2S, SWE4S, SWE6S, SWE8, SWE10, SWE12, SWE14, SWE16, SWE18, SWE20, SWE22, SWE24, SWE26, SWE28S, SWE30S, SWE32, SWE34, SWE36, SWE38, SWE40, SWE42, SWE44S, SWE46, SWE48, SWE50, SWE52, SWE54, SWE56, SWE58, SWE60S, SWE62, SWE64, SWE66, SWE68, SWE70, SWE72, SWE74, SWE76, SWE78, SWE80, SWE82, SWE84, SWE88S, SWE90S, SWE92S, SWE94S, SWE96S, SWE98, SWE100, SWE106, SWE108, SWE112, SWE114, SWE118, SWE120S, SWE122, SWE124, SWE126, SWE128S, SWE130S, SWE132S

Feb 7, 03:53 AM PST - SFDC Communication: Configuration changes are taking place as part of the permanent fix. We have engaged a third-party network vendor to assist with the longer-term fix. The mitigation steps have further reduced the network traffic load, and some customers have confirmed that they no longer see any impact. We continue to monitor the progress. 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.