Service Disruption

The Salesforce Technology team has observed that performance is at the expected levels for SWE34, SWE36, and SWE114. The impact ended for SWE34 at 13:40 UTC, SWE36 at 13:49 UTC, and SWE114 at 13:51 UTC on July 18.

The upgrade is still in progress on SWE38, and the team continues to monitor this. We will provide an update following the upgrade or sooner if more information becomes available.

The Core App upgrade has begun, and the Salesforce Technology team is monitoring its progress. This upgrade is expected to take approximately 120 minutes to complete. We will provide an update following the upgrade or sooner if more information becomes available.

The Salesforce Technology team has confirmed that DEU100 and DEU122 are no longer impacted. The impact ended for DEU100 at 23:45 UTC on July 17 and for DEU122 at 00:20 UTC on July 18. The issue was self-resolved for these instances without any action being taken by the Salesforce Technology team. No further updates will be provided for these instances. Additional information will focus on the remaining instances that are still impacted

We will provide an update in one hour or sooner if more information becomes available.

The Salesforce Technology team has observed that as of 10:33 UTC, performance is at the expected levels for SWE118. The Core App upgrade, which successfully mitigated the impact, is now being performed on all other impacted instances.

We will provide an update in one hour or sooner if more information becomes available.

The Salesforce Technology team performed a Core App upgrade, which has yielded positive results. The team will continue monitoring and assessing whether this step resolves the impact. If this proves successful, this task will be performed across all impacted instances.

We will provide an update in one hour or sooner if more information becomes available.

The team is working on updating the Core Application version on a test instance to determine whether this will remediate the impact. In parallel, teams are also pursuing other paths, including reducing traffic to help progress the update. Upon further investigation, it was determined that customers are still in a service disruption state and have not entered into a performance degradation as previously stated. The incident also began earlier than previously thought. Impact began at 23:39 UTC on July 17, 2024. The team is continuing their investigation to understand the underlying cause.

We will provide an update in 2 hours or sooner if more information becomes available.

Upon monitoring, the teams have observed the impacted instances are still experiencing trailing performance degradation. Multiple teams are engaged and exploring multiple paths to resolution.

We will provide an update sooner or if more information becomes available.

The Salesforce Technology team continues to monitor the services, for instance, stability and performance levels.
We will keep you posted if additional information becomes available.
.

The Salesforce Technology team has completed the required workstreams. Monitoring and validation of instance stability and performance levels have now begun.

We’ll provide an update in 30 minutes or sooner if additional information becomes available.

To mitigate the impact, we are performing staggered rollbacks for the instances. We have reports that some instances are now out of impact. We will post individual updates for those instances to confirm the exact start and end times.

Please note: As we uncover more about other impacted cells, we will update our list of impacted instances.
We are actively investigating the issue and will provide an update in 30 minutes or sooner if more information becomes available.

At 01:48 UTC on July 18, 2024, the Salesforce Technology team noted a service disruption affecting multiple Hyperforce cells.
We identified an ongoing release as the likely trigger of the issue. To mitigate the impact, the team is performing a pre-task for a release rollback. During the service disruption, end users cannot access the service.
We are actively investigating the issue and will provide an update in 30 minutes or sooner if more information becomes available.