coreService Disruption on USA1230

What to do

• Check whether you use Salesforce coreService in usa1230. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 5h it lasted.

  Anything that failed between 2026-10-29 22:47 UTC and 2026-10-31 03:53 UTC may need a replay.

• Subscribe to Salesforce's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=salesforce works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Salesforce 5

1. updateOct 30, 2026, 9:29 PM UTC

   We're investigating an issue affecting connectivity between some Salesforce environments and Long-Term File Storage. Customers may experience delays or intermittent failures when accessing files, and org migrations are being impacted. Our teams are actively investigating and working to restore normal connectivity. We'll provide an update in 30 minutes or sooner if additional information becomes available.

   provider

2. updateOct 30, 2026, 9:54 PM UTC

   Engineering has identified a likely network configuration issue involving a recently added traffic-routing path. Some requests using this path are timing out when connecting to supporting services. Teams are evaluating two mitigation options: removing the new routing path or completing the required network permissions so traffic can flow successfully. As a precaution, planned migration activity involving the affected instance has been paused while mitigation is in progress. We'll provide an update in 30 minutes or sooner if additional information becomes available.

   provider

3. updateOct 30, 2026, 10:22 PM UTC

   Engineering identified a network-routing issue involving a recently added proxy path. Traffic sent through this path is intermittently failing because the required network permissions were not in place before traffic was enabled. Teams are preparing to remove the affected path from service so traffic uses the existing healthy route. Access to the cloud management console is currently unavailable, and Salesforce is engaging the cloud provider to restore access and proceed with the mitigation. Planned migration activity involving the affected instance remains paused as a precaution. We'll provide an update in 60 minutes or sooner if additional information becomes available.

   provider

4. updateOct 30, 2026, 10:58 PM UTC

   We've successfully applied a routing change in a test environment to remove the affected network path, and confirmed it did not disrupt connectivity. Teams are now gaining access to the production environment to apply the same change. We're also working to resolve a sign-in issue that is limiting internal access to the cloud management console needed for mitigation. We'll provide our next update upon a significant development.

   provider

5. updateOct 31, 2026, 6:41 AM UTC

   We have successfully validated and tested the fix. Initial reports indicate positive results, and services have returned to normal operating levels for the verification instances. We apologise for how you and your business may have been affected by this incident.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.