Changes / Salesforce / Service Disruption: Core Service
Salesforce: Critical incident: Service Disruption: Core Service
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Service Disruption: Core Service
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-09 04:24 UTC
Before: not present
After: 2026-07-09 09:50 UTC
Before: not present
After: 359 instances, Core Service
Before: not present
After: We're aware that some customers are unable to log into their sandbox environments due to unexpected multi-factor authentication (MFA) prompts. We’ve identified that a recent change is enforcing MFA and passkey verification and we’re preparing a rollback to restore services.
We'll provide an update in 30 minutes or sooner if additional information becomes available.
Before: not present
After: We've started rolling back the recent change and are monitoring the system to verify that expected login behavior is restored.
We’ve also identified a few additional impacted instances, and those have now been included in the Trust post. Customers on those instances will receive notifications going forward.
We're continuing to identify any other impacted instances and we'll provide an update in 30 minutes or sooner if additional information becomes available.
Before: not present
After: We've completed the rollback of the recent change, and service has been restored. Customers should now be able to log in to their sandbox environments as expected without unexpected multi-factor authentication (MFA) or passkey enforcement.
During the investigation, we identified that the start time is different from initially understood. We've updated the incident start time and the list of impacted instances to accurately reflect the scope of the issue.
We sincerely apologize for any inconvenience this may have caused to your business and appreciate your patience while we worked to resolve this.
Before: not present
After: Further investigations have confirmed that JPN4S, JPN8S, JPN24S, JPN154S, JPN172S, JPN182S, JPN184S, and KOR4S weren't impacted by this incident. We are removing these instances from the Trust post and apologize for any concern or inconvenience caused.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Service Disruption: Core Service (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON