Changes / Salesforce / Service Disruption: MANAGEDRUNTIMENVIRGINIA
Salesforce: Major incident: Service Disruption: MANAGEDRUNTIMENVIRGINIA
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: Service Disruption: MANAGEDRUNTIMENVIRGINIA
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-10-28 10:20 UTC
Before: not present
After: 2025-10-30 16:17 UTC
Before: not present
After: 1 instance, MANAGEDRUNTIMENVIRGINIA
Before: not present
After: We noted a service disruption impacting some Commerce Cloud customers between October 28 at 10:20 UTC and October 30 at 16:17 UTC. Customers who deployed a change during this time may have encountered 502 errors when accessing Storefronts and attempting to process orders.
We have identified a recent change as the trigger and performed a rollback, which remediated the impact. After a brief period of monitoring, we can confirm that customers should no longer experience 502 errors.
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.
Before: not present
After: After further investigation, we identified that customers who deployed changes during this time may have encountered 502 errors related to the Managed Runtime Redirects feature, which could have affected access to Storefronts. Order processing was not impacted.
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: Service Disruption: MANAGEDRUNTIMENVIRGINIA (this change) | Major incident |
All Salesforce changes → · Salesforce profile · Markdown · JSON