Rewindex

CompaniesSalesforceIncidents

Salesforce: Feature Service Disruption: Search

MinorStatus: resolvedStarted Resolved (16 min)1 updatestatus.salesforce.com (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Salesforce’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +3 h 10 min vs the first vendor naming Cloudflare)

Swipe sideways to see the whole diagram.

same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Salesforce (this incident)posted +3 h 10 min
same windowCloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Salesforce (this incident)posted +3 h 10 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["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Salesforce (this incident)<br/>posted +3 h 10 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: Search179 instances

Timeline of updates

  1. update

    Starting at 14:40 UTC, we noted a feature disruption impacting the search functionality across multiple instances. During this time, customers may have experienced issues with using the search feature, including search indexing. The issue self-resolved without any manual intervention at 14:56 UTC. We apologize for any inconvenience this issue may have caused you and your business. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

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