Salesforce: Performance Degradation: Core Service

MinorStatus: resolvedStarted 2026-10-20 07:50 UTCResolved 2026-10-20 07:58 UTC (8 min)0 updatesstatus.salesforce.com

Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

Salesforce’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h 42 min vs Google Cloud’s own post)

Swipe sideways to see the whole diagram.

Salesforce is outlined in red. Groups show up to a few vendors each; the event page lists every incident.

Mermaid source

flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  me["Salesforce (this incident)<br/>posted +1 h 42 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 Service1 instance

Timeline of updates

The vendor published no update text for this incident.

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

Salesforce profile Recent Salesforce incidents Markdown JSON