Feature Disruption

We’re continuing to review each step of the cross-instance connection request paths, but have yet to pinpoint a defined trigger. We’ve identified a recent endpoint configuration change that may align with the impact start and are looking into this further.

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

We’ve determined that cross-instance network connectivity between the impacted sandbox environments and the production destination is stable and operating as expected. Efforts continue to narrow down the trigger for the change set upload failures.

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

We continue to reproduce and debug, and have engaged additional networking resources to allow us to get additional logging on the cross-instance change set call failures from sandbox to production.

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

KOR6 and ARE12 have been added to this post as a subset of customers on these instances are experiencing the issue. Customers in these instances will receive communications related to this incident going forward.

As we continue to investigate the trigger, we’ve identified a workaround that allows customers to proceed with the deployments from the sandbox to the production environment using a metadata API. Please refer to this Known Issue article for detailed instructions.

https://help.salesforce.com/s/issue?id=a02Ka00000gYHfh

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

The rollback to the next previous version is complete, and the issue remains, so recent releases have been ruled out as the trigger. We continue to investigate.

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

The rollback to a previous release version is complete, but the issue remains. We suspect that the previous release version may also contain the trigger for the issue, so we are rolling back the test instance to the next previous release version in order to verify. We’ve engaged additional resources to further investigate.

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

Upon further investigation, we have determined that the start time of impact is different than initially understood. We have now revised the start time to 23:00 UTC on June 26, 2025, to more accurately reflect the time customers may have begun to experience the impact.

The team has identified a recent release as the likely trigger for this issue. A rollback to the last known stable version is underway on a test instance to validate if this resolves the issue.

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

An issue is causing a “Connection is temporarily unavailable” error for a subset of customers when uploading a change set from the sandbox to the production environment. We are investigating the issue.

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