Skip to main content
Chrome icon

New! Check service status instantly with our Chrome extension

Add to Chrome External link icon
Firefox icon

New! Check service status instantly with our Firefox extension

Add to Firefox External link icon
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    Sign up
    Salesforce icon
    Salesforce icon

    Salesforce outage history

    AI-powered CRM platform for unified customer management and analytics.

    There were 778 Salesforce outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Not working for you?

    major icon Major

    : Salesforce core service disruption affects three North American instances

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (35 minutes)

    Salesforce listed core service disruptions affecting USA356, USA464, and USA1272 at . The update said the ComplianceQuest managed packages had been re-enabled following a security advisory, restoring functionality for affected customers, while the ComplianceQuest connected apps remained disabled pending security remediation. Salesforce marked the affected core services restored by , though the connected app integrations remained unavailable.

    minor icon Minor

    : Salesforce Data 360 issues disrupt batch transforms and AI functions

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 hours and 10 minutes)

    Salesforce reported degraded Data 360 performance starting at , affecting instances across North America, EMEA, and Asia Pacific. Customers could be unable to run batch transforms, while AI functions relying on tenant-based models, including Extension Functions, could fail when model downloads did not complete. Salesforce later expanded the listed impact to another instance after finding the issue affected a broader set of customers than first understood.

    Salesforce identified a recent release as a possible trigger and began rolling it back, first through testing environments and then in production. Customers could continue to see failures during deployment; Salesforce marked the affected instances recovered at , about three hours after the incident was reported.

    minor icon Minor

    : Salesforce MuleSoft and Marketing Cloud features face disruption

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (2 days, 22 hours and 6 minutes)

    Salesforce reported a US-region disruption affecting MuleSoft API Manager, Runtime Manager, and Partner Manager at . Customers were unable to deploy applications and APIs, some saw errors loading the interface, and authentication requests timed out. Salesforce said retries could succeed for some customers and began investigating; authentication response times had returned to normal by about , with errors declining. The impact was later found to extend to Composer and Secrets Manager. Most affected MuleSoft features were restored by .

    Salesforce also reported an email content publishing issue affecting some Marketing Cloud Growth & Advanced Editions instances. Fixes were deployed over several days, though a subset of customers still needed a workaround while Salesforce completed cleanup. Affected instances were listed as restored by . These were partial feature disruptions rather than a complete Salesforce outage.

    minor icon Minor

    : Salesforce incidents disrupt Setup, MuleSoft, and email publishing

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 days, 3 hours and 56 minutes)

    Salesforce customers on some instances saw slower Setup pages, longer load times, and intermittent timeouts starting around . Salesforce investigated a recent change as a possible trigger and expanded the affected-instance scope; the listed Core Service instances had recovered by . Separately, an email content publishing issue affected some instances, with Salesforce deploying a fix and completing remaining cleanup by . Salesforce noted that a subset of customers might still be unable to publish email during cleanup and could use a workaround.

    Later on Nov. 13, a MuleSoft issue affected API Manager, Runtime Manager, Partner Manager, and related features in the US region. Customers were unable to deploy applications and APIs, some saw errors loading the interface, and authentication requests timed out. Salesforce reported improving service and normal authentication response times, then cleared the listed affected components by . Overall, these were partial disruptions rather than a complete Salesforce outage.

    minor icon Minor

    : Salesforce Spiff email publishing disrupted across affected instances

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 days, 11 hours and 41 minutes)

    Salesforce Spiff customers had trouble publishing email content, with some messages stuck in Publishing or Processing. Salesforce identified a potential cause and began rolling out a fix after the disruption was reported at . The rollout was staged across affected instances, and Salesforce advised customers awaiting the fix to use a workaround in its Known Issue article.

    By , Salesforce said the fix was in place on impacted instances, though some customers could still be unable to publish while final cleanup continued. The affected instances were subsequently marked recovered at .

    minor icon Minor

    : Salesforce Agentforce connection errors affect mobile integrations

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 days, 17 hours and 51 minutes)

    Customers using the Agentforce mobile SDK and Life Sciences iPad application were unable to connect to Agentforce, with some seeing missing-session or tenant-key errors. Salesforce later traced the issue to an authentication configuration that stopped passing a required identifier. The connection errors began as early as and affected instances across North America, EMEA, and Asia Pacific.

    Salesforce investigated a possible release-related cause, then prepared and tested a configuration change to restore the missing identifier. It began rolling out the fix to affected production instances on November 12, and many instances were reported recovered by . Salesforce said the rollout was continuing for the remaining impacted instances, so recovery was gradual rather than a single service-wide restoration.

    minor icon Minor

    : Salesforce feature disruptions affect scheduling, Agentforce and email publishing

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (3 days, 18 hours and 36 minutes)

    Salesforce reported several feature-level disruptions across its products. Starting at , Field Service Lightning customers in sandbox environments could not view or use custom actions in the Dispatch and Scheduling Console, potentially blocking sandbox deployments; production was not affected. Salesforce paused a release and rolled it back, and the affected Field Service instances were marked restored by . Separately, some customers could not connect to Agentforce through mobile SDK and Life Sciences iPad integrations, while email content publishing and Salesforce Spiff also had issues. Agentforce connection errors were traced to an authentication configuration that stopped passing a required identifier, and Salesforce deployed a corrective change across affected instances.

    The incidents affected specific features and instances rather than making Salesforce broadly unavailable. Salesforce continued rolling out fixes and posting progress updates; some email publishing instances still needed cleanup as of , and a subset of customers could remain unable to publish. Salesforce marked many Marketing Cloud Growth and Advanced Editions instances restored at .

    minor icon Minor

    : Salesforce feature disruptions affect Apex, Agentforce, and email publishing

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 days, 12 hours and 46 minutes)

    Salesforce initially marked numerous core instances as down at , then revised the incident to a feature disruption. Customers on some recently updated instances experienced intermittent failures compiling or deploying Apex code, and in some cases could not log in or complete processes that depended on that code. Salesforce identified a runtime-library change as the likely trigger and rolled affected instances back, with recovery confirmed on prioritized instances as the rollback progressed.

    minor icon Minor

    : Salesforce feature disruptions affect Apex, Agentforce and email publishing

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 days, 12 hours and 51 minutes)

    From through , Salesforce reported several separate, partial disruptions rather than a platform-wide outage. Customers on affected instances encountered intermittent failures compiling or deploying Apex code; Agentforce connection errors blocked some mobile SDK and Life Sciences iPad users; and some Marketing Cloud Growth & Advanced Editions customers could not publish email content. Field Service Scheduling custom actions were also unavailable in sandbox environments, while Salesforce said production was unaffected. Salesforce traced several issues to recent software or configuration changes and worked through rollbacks and fixes, updating customers as deployments progressed.

    Salesforce also reported a Heroku Private Spaces issue in Tokyo that prevented some customers from restarting dynos or scaling up, though running dynos were not expected to be affected. The Field Service sandbox issue and several other instance-level disruptions were later cleared, but the email-publishing fix was still awaiting final cleanup on some instances in the latest update on . Salesforce said some customers might remain unable to publish while that work was completed and provided a workaround.

    major icon Major

    : Salesforce disruptions affect Apex, Agentforce, and other services

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 days, 4 hours and 26 minutes)

    Salesforce reported several separate disruptions across its products from to . On Nov. 11, many Salesforce instances were affected by intermittent failures compiling or deploying Apex code; some customers also had trouble logging in or completing processes that relied on the affected code. Salesforce rolled back a recent release, and affected instances were reported recovered by . Separately, Runtime Fabric customers who manually upgraded applications could lose monitoring logs, metrics, and metering data, although their applications continued running.

    Salesforce icon

    Looking for more Salesforce outage stats?

    Get real-time insights and historical data on Salesforce outages.

    Salesforce outage stats