rewindex

CompaniesSalesforceIncidents

Salesforce: Service Disruption: Core Service

MajorStatus: resolvededitedStarted Resolved (5.0 h)9 updatesstatus.salesforce.com (opens in new tab)

Affected components: Core Service4 instances

Timeline of updates

  1. update

    We're aware of an issue impacting multiple Salesforce instances. Since approximately 20:59 UTC, customers on affected instances may have been unable to log in or access their services. We've engaged our third-party partners to assist in the investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  2. update

    We've determined that the issue is not due to a third-party service disruption. We're now investigating recent changes that may be related, and we're working to find the best path to resolution.

  3. update

    As a precaution, we've started reverting a recent change to return it to its previous working state, and we're investigating other possible causes.

  4. update

    We're still reverting the recent change we identified, and we're continuing to investigate other possible causes.

  5. update

    We're still reverting the recent change, and we're now investigating our network infrastructure.

  6. update

    We're making progress on rolling back the recent change, and we're also reviewing other recent changes that may be related.

  7. update

    We have completed a rollback of the recent network configuration change in a lower environment and are working through the remaining validation steps before applying the update to production.
    We'll continue to provide updates as our investigation progresses.

  8. update

    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.

  9. update

    Once we successfully completed the validation steps in the lower environment, and confirmed connectivity was restored. We applied the same fix to the production environment and confirmed customers on affected instances can now log in and access their services. This issue is now resolved.

    We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

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