Global Outage Map
← Live dashboard
Salesforce

mule Soft Feature Degradation (20004586)

ResolvedminorOfficial source confirmedFirst recorded update 09-11-2026 23:59 · Resolved 10-11-2026 01:45

Customers using MuleSoft application programming interfaces (APIs) protected by service level agreement (SLA)-based rate limiting policies can now make requests successfully, without receiving 401 Unauthorized (access denied) errors. We deployed the fix to all impacted regions. We completed validation and confirmed that services are restored. We apologize for how this incident affected you and your business. We will complete a full investigation to establish the technical trigger and underlying cause, and to put preventive actions in place so this doesn't happen again.

Salesforce live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments
    Having problems with Salesforce now? Check the current status

    Updates (2)

    1. 10-11-2026 02:00
      mule Soft Feature Degradation (20004586)

      Customers using MuleSoft application programming interfaces (APIs) protected by service level agreement (SLA)-based rate limiting policies can now make requests successfully, without receiving 401 Unauthorized (access denied) errors. We deployed the fix to all impacted regions. We completed validation and confirmed that services are restored. We apologize for how this incident affected you and your business. We will complete a full investigation to establish the technical trigger and underlying cause, and to put preventive actions in place so this doesn't happen again.

      Salesforce ↗
    2. 10-11-2026 00:54
      mule Soft Feature Degradation (20004586)

      Customers using MuleSoft application programming interfaces (APIs) protected by Service Level Agreement (SLA)-based rate limiting policies may receive "401 Unauthorized" errors, even with valid client credentials. As a result, API calls are rejected. This affects CloudHub 1.0, CloudHub 2.0, and Hybrid runtimes. We identified an issue with a feature setting and began deploying a fix at 23:30 UTC. We'll confirm once the fix is complete and the errors stop. We'll provide an update in 30 minutes or sooner if additional information becomes available.

      Salesforce ↗

    What to do next

    • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
    • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
    • Watch the provider going forward. Follow Salesforce's status feed →

    GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.