Minor impactResolvedDevOps

LaunchDarkly incident: Flag Updates delayed in US Region

LaunchDarkly reported this minor-impact incident on its official status page on Aug 14, 2026, 14:47 UTC. It was resolved after 2h.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Aug 14, 2026, 14:47 UTC
started
Aug 14, 2026, 16:47 UTC
resolved
2h
duration
Minor
impact

Affected components

  • Client-side streaming API

Timeline

updates from LaunchDarkly's status page ↗
  1. resolvedAug 14, 2026, 16:47 UTC

    The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.

  2. monitoringAug 14, 2026, 16:05 UTC

    We investigated elevated error rates reported for mobile SDK flag delivery in US East. We've confirmed that flag delivery itself was not impacted. No customer action is required and we are monitoring the situation.

  3. investigatingAug 14, 2026, 14:47 UTC

    Flag Updates are currently delayed in the us-east-1 region. We are investigating the issue.

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.

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

← Previous: Elevated errors on server-side SDK streaming connections (Aug 7, 2026)Next: Flag Updates via Polling API delayed (Aug 17, 2026) →
LaunchDarkly incident on Aug 14, 2026: Flag Updates delayed in US Region · APIStatus.watch