Changes / Salesforce / Heroku Service Disruption: Data
Salesforce: Major incident: Heroku Service Disruption: Data
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: major (vendor)Changed Detected Source: status.salesforce.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: Heroku Service Disruption: Data
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-08 00:25 UTC
Before: not present
After: 2026-05-08 17:17 UTC
Before: not present
After: 1 instance, Data
Before: not present
After: Beginning at 00:25 UTC on May 08, 2026, a partial outage in an upstream service provider began impacting a subset of customers in the US region. Affected customers may be experiencing intermittent connectivity, elevated DB latency, or degraded performance with third-party add-on providers.
Affected customers may wish to trigger database failovers as a mitigation.
Before: not present
After: Engineers are working to restore impacted resources. While the partial outage from the upstream service provider is ongoing, some customers are observing signs of recovery. Upstream resources remain impacted, and our team continues to work toward full resolution.
Before: not present
After: Engineers are working to restore impacted resources. While the partial outage from the upstream service provider is ongoing, the majority of customers are observing recovery. Upstream resources remain impacted, and our team continues to work toward full resolution. We will post another update in approximately 2 hours.
Before: not present
After: Engineers continue working on restoring impacted resources. While the partial outage from the upstream service provider is ongoing, we are seeing little customer impact. Upstream resources remain impacted, and our team continues to work toward full resolution.
Before: not present
After: Engineers continue working on restoring impacted resources. While the partial outage from the upstream service provider is ongoing, we are seeing little customer impact. Upstream resources remain impacted, and our team continues to work toward full resolution. We will post an update in approximately 2 hours, or if anything changes sooner.
Before: not present
After: We’ve completed the migration to a new availability zone, and the Heroku-hosted web applications and customer databases are now fully operational.
We apologize for how this incident affected you and your business. We'll undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Before: not present
After:
While the majority of customers are now out of impact, we’ve determined that a small subset of customers may still be experiencing a read-only state with their databases. We're actively working to restore full functionality for all remaining affected customers. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Before: not present
After: We've confirmed a remediation path, and are applying the fix to the small subset of customers still experiencing a read-only state. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Before: not present
After: We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. 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.
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: Heroku Service Disruption: Data (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON