rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident silently edited: Service Disruption: Core Service

Silent editNormal progress (typesafe/jev-1.13-20260917, 83%)Changed status.salesforce.com (opens in new tab)
Summary

Salesforce edited its 10-30 22:58 UTC Core Service disruption update: a routing change removing the affected network path passed testing without disrupting connectivity, but production rollout was still pending. A sign-in issue continued to limit internal cloud management console access needed for mitigation; service restoration was not confirmed.

Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.

Incident page: the full timeline of updates

What changed

Struck in red is what Salesforce removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateupdate#1
Before: We’ve confirmed that some traffic is being routed through a newly added network path before its addresses are authorized by dependent services. Requests using this path may time out or fail intermittently. Teams are working with our third-party service provider and internal access teams to restore administrative console access needed for mitigation. Once access is available, Engineering plans to remove the affected route in a test environment, validate that connectivity recovers, and then apply the change to production. Alternative mitigations include potentially disabling the new proxy cluster or completing the required network permissions. We'll provide an update in 60 minutes or sooner if additional information becomes available.
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdaySaturday, October 31Sat, Oct 31

1 rewrite, 1 incident change

Friday, October 30

3 incident changes

Thursday, October 29

1 incident change

All Salesforce changesSalesforce profileMarkdownJSON