LaunchDarkly Outage History

The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.

Monitoring has confirmed no further impact outside of the initially reported 7:30-7:37pm PT timeframe

The incident has been resolved and the flag dashboard is successfully loading.

We have confirmed Slack notifications are now coming through for segment approvals again.

This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused.

All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.

We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.

All experiment and multi-armed bandit result data is caught up. No data was lost.

This incident has been resolved.

Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.

We've identified elevated error rates with server-side streaming initialization requests in the APAC region between 19:52 and 19:56 PT. Some customers may have experienced initialization timeouts despite SDK retries.

We've caught up on the streaming data export backlog.

We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.

We have validated a fix to resolve all remaining experiments with inaccurate sample ratio mismatches (SRMs) or empty experiment results. The vast majority of experiments and experimentation customers were not impacted.

Observability alerts are functioning and delayed alerts have been redelivered.

We've fully caught up on the metrics data backlog.

We're addressing an issue that prevented warehouse data export from 12pm to 6pm PT on April 23 and are working to backfill that data to customer warehouses.

This incident has been resolved.

The issue has been resolved.

Between approximately 9:37 PM and 9:46 PM PT on April 9, 2026, some customers using server-side SDKs in the EU region may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly. The issue resolved. No action is required from customers. Server-side SDKs automatically reconnect and recover from transient connectivity issues.

Server-side streaming began rejecting new connections across all commercial regions, causing 500/503 errors for customers attempting to establish new SDK streaming connections for a brief period of time. Detailed timelines of the incident: - us-east-1 : 7:53 AM PST to 8:24 AM PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.

Our team completed the data restoration for previously affected experiment iterations. Complete data is now available for all experiment iterations in the UI.

The issue with Event processing has been resolved. Impacted services have returned to normal operation. Flag Delivery was not impacted. There was no data loss experienced.

We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.