rewindex

ChangesSalesforceService Disruption: Core Service

Salesforce: Incident updated: Service Disruption: Core Service

Incident updateNormal progress (rule, 100%)Changed status.salesforce.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

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.

AddedUpdateupdate#1
Before: not present
After: 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.

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

TodaySaturday, October 31Sat, Oct 31

1 rewrite, 1 incident change

YesterdayFriday, October 30Fri, Oct 30

3 incident changes

Thursday, October 29

1 incident change

All Salesforce changesSalesforce profileMarkdownJSON