← Blog

Fastly Data Breaches: Full Timeline Through 2026

Share on X

People search Fastly data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Fastly-linked incident. This page maps every attested event through 2026 with internal links to canonical records.

Why Fastly breach history matters

Fastly operates in Software (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.

Full timeline through 2026

2025 — — "Fastly was impacted by the recent security incident…

Cataloged incident. "Fastly was impacted by the recent security incident involving Salesloft's Drift application. We have investigated and notified all Fastly customers affected. This incident was isolated to our Salesforce instance and did not impact any Fastly services, infrastructure, or products. This post includes a summary of our response and the customer outreach we’ve performed. What Happened Between August 13 and August 18, 2025, a threat actor (tracked as UNC6395 by Google Mandiant) exploited stolen OAuth tokens tied to th Exposed categories include Unknown. No attested victim count is published for this row yet. See the fastly2025-vcdb1 and canonical BreachHistory entry.

Patterns and analysis

  • Mixed intrusion and disclosure events — appears across multiple Fastly catalog entries; prioritize controls that address this class of failure.
  • Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
  • 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.

What to do if you may be affected

  1. Step 1: Enable phishing-resistant MFA on every account tied to this brand.
  2. Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
  3. Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
  4. Step 4: Bookmark the Fastly company page for new 2026+ disclosures.

Canonical BreachHistory hub

Explore every indexed row: breachhistory.com/fastly · Latest: fastly2025-vcdb1.

Sources: BreachHistory catalog (1 rows for Fastly), company and regulator disclosures cited in individual breach records.