LaunchDarkly Outage History

LaunchDarkly experienced elevated streaming initialization error rates in the APAC region for 30 minutes, caused by an infrastructure issue. Customers using streaming server-side SDKs experienced longer than normal initialization times or timeouts when connecting to the service. The issue was resolved by implementing a fix that restored normal streaming SDK connectivity.

LaunchDarkly experienced delays in experiment and multi-armed bandit results, with data delayed by 1-2 hours during the incident. The service identified and implemented a fix to resolve the processing backlog. All experiment data was fully caught up within 41 minutes with no data loss.

LaunchDarkly experienced elevated streaming errors in the Europe region for 6.2 hours, caused by an infrastructure issue that affected the Streaming API. Customers using streaming server-side SDKs experienced longer than normal initialization times or timeouts when connecting to the service. The issue was resolved after implementing a fix that restored normal streaming SDK connectivity.

LaunchDarkly experienced a 6.4-hour incident that caused delays in experimentation results processing and data warehouse export functionality. The service identified the root cause and implemented a fix, then worked through a backlog of delayed data processing. The issue was fully resolved when all experimentation results and data warehouse exports were caught up.

LaunchDarkly experienced a 45-minute delay in streaming data export delivery caused by latency issues in their Pub/Sub export system. Customers using streaming data export experienced multi-minute lags in receiving their data, though no data was lost during the incident. The issue was resolved by addressing the Pub/Sub latency and clearing the accumulated export backlog.

LaunchDarkly experienced an issue where editing flag variations between experiment iterations caused sample ratio mismatches (SRMs) or empty experiment results for some customers. The service implemented a fix to prevent the issue in new experiments and then validated a complete resolution for all affected experiments. The incident lasted 27.9 hours and impacted only a small subset of experimentation customers.

LaunchDarkly experienced a 54-minute outage where Observability alert notifications failed to be delivered to users. The engineering team identified the root cause, deployed a fix, and redelivered all delayed notifications. All other notification types remained operational throughout the incident.

LaunchDarkly experienced a metrics ingestion delay in the EU region that caused under-reporting of customer metrics for approximately 16 minutes (11:11-11:27am ET). The service team identified the issue, confirmed no data was lost, and spent 2 hours processing the backlogged metrics data. The incident was fully resolved once all delayed metrics were successfully ingested and caught up.

LaunchDarkly's documentation site experienced a major outage for 27 minutes due to an issue with their documentation provider. The incident was identified as being linked to an outage on the doc provider's side, and a fix was implemented to restore service.

LaunchDarkly experienced an issue where observability alerts failed to deliver Slack notifications to channels, though direct message alerts continued working normally. The problem was identified after approximately 1.5 hours of investigation and fully resolved after 2.3 hours total duration.