rewindex

CompaniesSalesforceIncidents

Salesforce: Service Disruption: Core Service

MajorStatus: resolvededitedStarted Resolved (29 h)5 updatesstatus.salesforce.com (opens in new tab)

Affected components: Core Service1 instance

Timeline of updates

  1. update

    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.

  2. update

    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.

  3. update

    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.

  4. updateEdited

    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.

  5. update

    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.

Changes Rewindex caught on this incident

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.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).

Salesforce profileRecent Salesforce incidentsMarkdownJSON