Changes / Salesforce / Maintenance Overrun Service Disruption Began: Core Service
Salesforce: Major incident: Maintenance Overrun Service Disruption Began: Core Service
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 74%)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Maintenance Overrun Service Disruption Began: Core Service
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-18 17:00 UTC
Before: not present
After: 2026-04-18 19:39 UTC
Before: not present
After: 1 instance, Core Service
Before: not present
After: At 18:35 UTC on April 18, 2026, the service disruption affecting the AP52 instance was resolved. Customers should now be able to access their Salesforce services as expected. We will now remove the AP52 instance from this Trust posting and they will receive a separate post to accurately reflect the correct impact times.
We are continuing to work on restoring the remaining impacted instance (AP62) and the next update will be upon a significant change in status, or sooner if additional information becomes available.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Maintenance Overrun Service Disruption Began: Core Service (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON