Minor impactResolvedDevOps

LaunchDarkly incident: Elevated error rates on event data ingestion endpoints

LaunchDarkly reported this minor-impact incident on its official status page on Jul 3, 2026, 14:29 UTC. It was resolved after 1h 37m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jul 3, 2026, 14:29 UTC
started
Jul 3, 2026, 16:06 UTC
resolved
1h 37m
duration
Minor
impact

Affected components

  • AI insights
  • Experiment results processing
  • Flag usage metrics
  • Metrics
  • Rollout results analysis
  1. resolvedJul 3, 2026, 16:06 UTC

    This incident has been resolved.

  2. monitoringJul 3, 2026, 15:13 UTC

    A fix has been implemented and we are monitoring the results.

  3. investigatingJul 3, 2026, 14:29 UTC

    We are investigating elevated error rates on our event data ingestion endpoints affecting production customers, between approximately 7:00 AM PDT and 7:15 AM PDT. During this window, a portion of feature flag, experimentation, and AI/agent event data may have been rejected or delayed. Flag delivery and evaluation are not affected. SDKs continue to serve flags normally. Observability ingest is not affected.

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

LaunchDarkly incident on Jul 3, 2026: Elevated error rates on event data ingestion endpoints · APIStatus.watch