Rewindex

RewindexOutage eventsSep 16, 2026

Salesforce outage, Sep 16, 2026

15 vendors posted 14 incidents between 07:00 and 19:00 UTC, against about 54 incidents from 37 vendors in the same hours on an ordinary week. 5 vendors named Salesforce in 5 incidents (5 of them blamed it). Salesforce posted “Performance Degradation: Core Service” at 07:19 UTC.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when Salesforce posted (07:19).

    25. Salesforce posted 07:19
Named SalesforceNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Salesforce, grouped by when they posted, and vendors that blamed one of the vendors Salesforce took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Salesforceposted 07:19 UTC1 to 4 hours later4 vendors, 4 blamed SalesforceBraze, Gong, ClickHouse Cloud, SmartsheetLater1 vendor, 1 blamed SalesforceSalesloft
Salesforceposted 07:19 UTC1 to 4 hours later4 vendors, 4 blamed SalesforceBraze, Gong, ClickHouseCloud, SmartsheetLater1 vendor, 1 blamed SalesforceSalesloft
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Salesforce<br/>posted 07:19 UTC"]:::root
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Salesforce<br/>Braze, Gong, ClickHouse Cloud, Smartsheet"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed Salesforce<br/>Salesloft"]:::blames
  root --> later

Vendors that named Salesforce

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

1 to 4 hours later

4 vendors

  • +1 h 59 min

    Blames Salesforce

    Critical incident

    BrazeBraze Support Services Outage

    …erator as usual. We have confirmed stable service following remediation of the underlying Salesforce Service Cloud issue. Braze Support Services and Partner Portal are currently experiencing issues du…

  • +2 h 5 min

    Blames Salesforce

    Minor incident

    GongGong CRM is currently affected by a service disruption at Salesforce

    …Gong CRM is currently affected by a service disruption at Salesforce The issue has been resolved. The issue has been resolved. We are currently monitoring system recovery following an update from our…

  • +2 h 57 min

    Blames Salesforce

    Minor incident

    ClickHouse CloudIntermittent Issues with the Support tab

    …Intermittent Issues with the Support tab Salesforce has confirmed the incident is resolved on their end. Salesforce has confirmed the incident is resolved on their end. We are currently in monitoring…

  • +3 h 18 min

    Blames Salesforce

    Major incident

    SmartsheetSalesforce connector is experiencing intermittent issues

    …Salesforce connector is experiencing intermittent issues On September 16th, 2026, starting at approximately 3:36 AM PDT, customers began experiencing intermittent errors with the Salesforce Connector…

Later

1 vendor

Same window, did not name anyone

9 incidents started during the event without naming Salesforce or another vendor. Some are part of it, some are a normal day’s background (about 54 in these hours).

Show all 9

Detected automatically from 13 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.