Performance Degradation

As of 17:56 UTC, all impacted sandbox instances have been confirmed as being out of impact. The fix is continuing to be rolled out to all other impacted instances.

We’ll provide an update once the rollout is complete or if new information becomes available.

A fix has been successfully tested and is being rolled out to all impacted instances. The deployment is expected to take several hours to complete.

We’ll provide an update once the rollout is complete or if new information becomes available.

Our team is currently testing the fix on one of the impacted instances. Once the fix is successfully tested, it will be rolled out to all the affected instances.

We’ll provide an update as soon as additional information becomes available.

We have determined that this issue is impacting additional packages as well, requiring a larger-scale solution that is in the process of being implemented.

We’ll provide an update as soon as additional information becomes available.

We are continuing to investigate the trigger for this issue and work to validate a suitable resolution as quickly as possible.

We’ll provide an update as soon as additional information becomes available.

We are continuing to investigate what triggered this incident and work to resolve it as quickly as possible. A fix has been developed and is currently being validated as a suitable resolution.

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

Our teams are investigating and believe the trigger to be related to a network configuration issue. A temporary solution is being implemented to minimize impact while we work on a permanent fix.

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

At 00:00 UTC on April 25, the Salesforce Technology team noted a performance degradation on multiple instances. Customers with orgs on impacted instances cannot install or upgrade S-Docs packages and get an error message that reads, "The requested package was not found." Our team is currently investigating this issue.

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

We are investigating a potential cause of the issue.