Rewindex

CompaniesSalesforceIncidents

Salesforce: Performance Degradation: Core Service

MinorStatus: resolvedStarted Resolved (37 min)2 updatesstatus.salesforce.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents

Salesforce’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted −19 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud, JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeSalesforce (this incident)posted −19 min
same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud,JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeSalesforce (this incident)posted −19 min
Salesforce is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later
  me["Salesforce (this incident)<br/>posted −19 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Core Service84 instances

Timeline of updates

  1. update

    Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.

  2. update

    We’ve investigated and confirmed resolution of a third party performance degradation that impacted multiple Salesforce instances. Impacted customers may have experienced latency and errors. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).

Salesforce profileRecent Salesforce incidentsMarkdownJSON