Rewindex

CompaniesLaunchDarklyIncidents

LaunchDarkly: Delays for Customers Using the Cloudflare Edge SDK

MinorStatus: resolvedStarted Resolved (3.1 h)1 updatestatus.launchdarkly.com (opens in new tab)
Part of an outage event

Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents

LaunchDarkly’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +52 min vs the first vendor naming Google Cloud)

Swipe sideways to see the whole diagram.

blamed Firebaseblamed Anthropicblamed Cloudflaresame windowGoogle Cloudown incident not archivedWithin an hour29 vendors, 28 blamed GoogleCloudPinecone, Northflank, imgix +261 to 4 hours later12 vendors, 11 blamed GoogleCloudSmartsheet, Daily, Confluent +9Later1 vendor, 1 blamed GoogleCloudZillizFirebaseown incident not archivedCodeium, Windsurf+13 minAnthropicposted +28 min, did not nameGoogle CloudGitHub, GitHub Copilot+24 minCloudflareown incident not archivedDoppler, Jupyter (Anaconda),Socket +4+35 min to +3 h 41 minLaunchDarkly (this incident)posted +52 min
blamed Firebaseblamed Anthropicblamed Cloudflaresame windowGoogle Cloudown incident not archivedWithin an hour29 vendors, 28 blamed GoogleCloudPinecone, Northflank, imgix +261 to 4 hours later12 vendors, 11 blamed GoogleCloudSmartsheet, Daily, Confluent +9Later1 vendor, 1 blamed GoogleCloudZillizFirebaseown incident not archivedCodeium, Windsurf+13 minAnthropicposted +28 min, did not nameGoogle CloudGitHub, GitHub Copilot+24 minCloudflareown incident not archivedDoppler, Jupyter (Anaconda),Socket +4+35 min to +3 h 41 minLaunchDarkly (this incident)posted +52 min
LaunchDarkly 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>29 vendors, 28 blamed Google Cloud<br/>Pinecone, Northflank, imgix +26"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>12 vendors, 11 blamed Google Cloud<br/>Smartsheet, Daily, Confluent +9"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed Google Cloud<br/>Zilliz"]:::blames
  root --> later
  p0["Firebase<br/>own incident not archived"]:::inferred
  root -.-> p0
  k0["Codeium, Windsurf<br/>+13 min"]:::hop2
  p0 -->|"blamed Firebase"| k0
  p1["Anthropic<br/>posted +28 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["GitHub, GitHub Copilot<br/>+24 min"]:::hop2
  p1 -->|"blamed Anthropic"| k1
  p2["Cloudflare<br/>own incident not archived"]:::inferred
  root -.-> p2
  k2["Doppler, Jupyter (Anaconda), Socket +4<br/>+35 min to +3 h 41 min"]:::hop2
  p2 -->|"blamed Cloudflare"| k2
  me["LaunchDarkly (this incident)<br/>posted +52 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.

Timeline of updates

  1. resolved

    Our partner has confirmed full restoration of their platform. We began observing full recovery starting at 2:07PM PT.

From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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.

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

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

LaunchDarkly profileRecent LaunchDarkly incidentsMarkdownJSON