Live  /  Salesforce  /  Incident

Salesforce: Degradation: APIFunctionalMonitoring, APIManager, AccessManagement (3 instances)

Salesforce · salesforce.comMinor incidentResolved2026-11-13 09:53 UTC
Public — what happened

Summary

Salesforce said that several MuleSoft services, including API Manager, Runtime Manager and Partner Manager, were having problems in the US region starting around 09:02 UTC on 2026-11-13. It reported that customers could not deploy applications or APIs, some saw errors loading the user interface, and requests to its authentication service were timing out. By 09:40 UTC the company said services were recovering and errors had dropped, though it was still looking into what triggered the problem. At 09:50 UTC it said more instances were affected than first understood, and the incident was still listed as under investigation and not resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Salesforce against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Salesforce: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Salesforce report →

More from Salesforce

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Salesforce status & history page.

Related: Salesforce status & history. SquidGrid is not affiliated with Salesforce.