Salesforce incident

The fix is progressing through our Emergency Release process and has entered the build process. We expect this process to take several hours, and we continue to closely monitor its progress.

Salesforce is currently experiencing a minor incident affecting AP52 and AP53 and 1 more component, which began 3h ago. The vendor's full update timeline is below.

Started
Jun 17, 2026, 10:34 AM UTC
Resolved
Ongoing
Duration
● 3h 24m
Detected by Pingoru
Jun 17, 2026, 10:34 AM UTC

Affected components

AP52AP53AP54AP58AP60ARE12ARE2SARE4SARE6AUS102

Update timeline

  1. identified Jun 17, 2026, 10:34 AM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Jun 17, 2026, 10:52 AM UTC

    We identified an issue introduced in a recent release that impacts the creation of new second-generation managed and unlocked package versions. Customers who develop and distribute applications on the Salesforce platform may be unable to create new versions of their managed or unlocked packages if those packages depend on another package that includes a connected app. This issue does not affect customers who are not creating new package versions or whose packages do not have this dependency. We’re developing and validating a fix before deployment. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Jun 17, 2026, 11:52 AM UTC

    We’ve verified a fix for this issue and are progressing through the Emergency Release process to obtain the necessary approvals for deployment. The fix requires a code change, which we are developing and validating in a test environment before deploying to production. This validation ensures the fix resolves the issue without introducing additional impact and will take some time to complete. Upon further investigation, we've determined that the start time of impact is different than initially understood. We’ve now aligned the start time to the recent release that went out during the weekend to more accurately reflect on Trust. We'll provide an update in 60 minutes or sooner if additional information becomes available.

  4. monitoring Jun 17, 2026, 12:35 PM UTC

    The fix is progressing through our Emergency Release process and has entered the build process. We expect this process to take several hours, and we continue to closely monitor its progress. Once the build completes, we'll deploy and validate the fix in a sandbox environment before proceeding with the broader deployment across all impacted instances. This validation will help ensure the issue is fully resolved before wider rollout. We'll provide our next update as soon as additional information becomes available.