Salesforce incident
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update once the fix has been deployed and validated, or sooner if we have more information.
Resolved after 3 hours, affecting AUS76 and BRA32 and 1 more, on May 20, 2026.
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update once the fix has been deployed and validated, or sooner if we have more information.
Affected components
Update timeline
- identified May 20, 2026, 01:38 AM UTC
Degradation Started: featureServiceDisruption
- monitoring May 20, 2026, 01:38 AM UTC
At 23:50 UTC on May 19, 2026 we began investigating a feature disruption impacting Salesforce Field Service (SFS) Mobile Services. Impacted customers may receive 403 error messages when trying to use the performance priming feature. We are in the process of deploying a fix to remediate the issue and this is expected to take approximately 60 minutes. We’ll provide an update in the next 60-90 minutes or sooner if new information, or validation of the fix, becomes available.
- monitoring May 20, 2026, 04:06 AM UTC
We’re working on implementing a fix that we believe will resolve the impact to customers. We will provide an update once the fix has been deployed and validated, or sooner if we have more information.
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