# Salesforce: Major incident: Service Disruption: Core Service

**Summary:** _summary pending_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-05-21 20:00 UTC · Detected: 2026-10-18 05:09 UTC
- [Source: https://status.salesforce.com/incidents/20004038](https://status.salesforce.com/incidents/20004038)
- [Company: Salesforce](https://rewindex.com/company/salesforce.md)
- Versions: before (none: first archived) → after incident\_version:130/20004038@e4704dac5f7d
- Change 1 of 1 for this incident

Incident page (full timeline): [Service Disruption: Core Service](https://rewindex.com/company/salesforce/incidents/20004038.md)
## What changed

**1. Added: Title**

```diff
+ Service Disruption: Core Service
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-05-21 20:00 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-05-22 01:37 UTC
```

**6. Added: Affected components**

```diff
+ 81 instances, Core Service
```

**7. Added: Update** (investigating) · 2026-05-21 22:02 UTC

```diff
+ We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
```

**8. Added: Update** (update) · 2026-05-21 22:30 UTC

```diff
+ At 20:00 UTC on May 21, 2026, a feature disruption began impacting the Salesforce Core Service in the NA223 instance. As a result, customers may be experiencing intermittent disruptions and degradations due to instability. We are engaged and are actively analyzing the issue to determine a mitigation pathway.  We'll provide an update in 30 minutes or sooner if additional information becomes available.
```

**9. Added: Update** (update) · 2026-05-21 23:15 UTC

```diff
+ We’ve identified a recent networking patch as the potential trigger. Some customers attempting to log in via login.salesforce.com or test.salesforce.com may be experiencing issues. We’ve initiated a reboot of impacted networking hosts as a possible solution. The team continues to analyze the trigger and explore additional remediation pathways. We'll provide an update in 30 minutes or sooner if additional information becomes available.
```

**10. Added: Update** (update) · 2026-05-21 23:16 UTC

```diff
+ 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.  
```

**11. Added: Update** (update) · 2026-05-22 00:37 UTC

```diff
+ Our investigations have highlighted that the impact radius is broader than initially understood. Please refer to https://status.salesforce.com/generalmessages/20000254 for all further communications about this issue.  We sincerely apologise for how this issue has impacted you and your business. 
```

**12. Added: Update** (update) · 2026-05-22 02:51 UTC

```diff
+ On May 21, 2026 at 20:00 UTC, customers geolocated in the USA East Region were unable to log in to their Salesforce services via login.salesforce.com and test.salesforce.com. Services that may have been affected include Core, CRM Analytics, Salesforce Maps, Marketing Cloud Account Engagement, and MuleSoft. We found that storage and system resource exhaustion caused instability. We cleared the affected systems and restarted impacted services to restore stability. These issues are now resolved and service access restored.  We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. 
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-05-21 20:00 UTC | Major incident: Service Disruption: Core Service (this change) | outage |

All Salesforce changes: [timeline](https://rewindex.com/company/salesforce/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/ic517ba88088cee · Markdown: https://rewindex.com/change/ic517ba88088cee.md · JSON: https://rewindex.com/api/v1/changes/ic517ba88088cee · Generated 2026-10-18T11:25:07.497Z