Salesforce incident

We have determined that the issue is occurring due to insufficient infrastructure capacity. In collaboration with our third-party provider, we have rolled back a recent change, and are now monitoring

Major Resolved View vendor source →

Salesforce experienced a major incident on May 5, 2026 affecting AUS102 and AUS14S and 1 more component, lasting 3h 12m. The incident has been resolved; the full update timeline is below.

Started
May 05, 2026, 01:00 AM UTC
Resolved
May 05, 2026, 04:12 AM UTC
Duration
3h 12m
Detected by Pingoru
May 05, 2026, 01:00 AM UTC

Affected components

AUS102AUS14SAUS16SAUS18SAUS20SAUS22SAUS24SAUS26SAUS28SAUS2S

Update timeline

  1. identified May 05, 2026, 01:00 AM UTC

    Disruption Started: salesforceDataCloudFeatureDisruption

  2. monitoring May 05, 2026, 01:00 AM UTC

    On May 1, 2026 at 15:15 UTC we detected a feature disruption impacting the Data Cloud CRM Connector. Customers may experience data stream jobs failing or getting stuck. We are investigating the issue to identify the cause and remediate the issue. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

  3. monitoring May 05, 2026, 01:54 AM UTC

    We are continuing to work on identifying the cause of the issue, including partnering with our third-party provider to analyze logs to identify the cause of the errors. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.

  4. monitoring May 05, 2026, 03:06 AM UTC

    We have determined that the issue is occurring due to insufficient infrastructure capacity. In collaboration with our third-party provider, we have rolled back a recent change, and are now monitoring how jobs are performing. We’ll provide another update in the next 60 minutes or sooner, if additional information becomes available.