LaunchDarkly incident: Flag Updates via Polling API delayed

Affected components

• Polling API

1. resolvedAug 17, 2026, 16:03 UTC

   This incident has been resolved.

2. monitoringAug 17, 2026, 15:29 UTC

   We've identified the root cause, our CDN provider had an issue on their end which is fixed now. Monitoring for a while to make sure things stabilise.

3. investigatingAug 17, 2026, 10:36 UTC

   We're experiencing a service degradation which can result in Flag updates via the Polling API to be delayed.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• GitHub: Incident with GitHub.comCritical · Aug 17, 2026, 13:40 UTC
• Elasticsearch: Increased error rates for microsoft-multilingual-e5-largeMajor · Aug 13, 2026, 08:32 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• CircleCI: GitHub Incidents impacting CircleCI functionalityMajor · Aug 17, 2026, 14:04 UTC
• Cursor: GitHub degradation affecting some Cursor services — Automations, Cloud Agents, CodebaseMajor · Aug 17, 2026, 14:34 UTC
• dbt Cloud: Git Failures in dbt PlatformMajor · Aug 17, 2026, 15:02 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• Contentful: Experience API experiencing issues on upsert operationsMinor · Aug 17, 2026, 09:05 UTC

How often does LaunchDarkly have incidents?

LaunchDarkly reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 19m. See LaunchDarkly's uptime and incident history