Salesforce incident
We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approac
Resolved after 2 hours 1 minute, affecting AP60, on June 14, 2026.
We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approach. Based on this success, we have initiated a rolling restart of all app servers on the AP60 instance. We will provide an update once the process is completed for all app servers or if additional information becomes available.
Affected components
Update timeline
- identified Jun 14, 2026, 06:34 AM UTC
Degradation Started: performanceDegradation
- monitoring Jun 14, 2026, 06:45 AM UTC
We are aware that customers on AP60 are experiencing a high volume of errors when performing actions such as saving records, creating new records, and updating records. Users may be able to retry operations to temporarily work around errors. We are actively investigating the technical trigger and our teams are working on remediation steps, including an app server restart. We will provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 14, 2026, 07:29 AM UTC
We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approach. Based on this success, we have initiated a rolling restart of all app servers on the AP60 instance. We will provide an update once the process is completed for all app servers or if additional information becomes available.
Your product runs on more than Salesforce
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services