LaunchDarkly

Affected: Feature workflows, Flag targeting, Segment management, Progressive rollouts, Release pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-15 15:47 UTC

   Between 15:11 and 15:32 UTC today, we observed elevated 5xx errors affecting requests across our services. Approximately 0.7% of requests failed during this period (99.3% succeeded). This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment management, Rollout management, Release pipelines

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-03 07:29 UTC

   Some automatic changes in LaunchDarkly are being applied later than expected. This affects stage transitions for guarded and progressive rollouts, release pipeline phase progression, and multi-armed bandit traffic reallocations. Delays began at approximately 4:15 PM PT on...

2. monitoring 2026-10-03 08:51 UTC

   The backlog of delayed changes has been fully processed as of 1:45 AM PT on October 3. All changes that were delayed during the incident have been applied. No data was lost. We are continuing to monitor.

3. resolved 2026-10-03 09:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Web app (app.launchdarkly.com)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-02 14:10 UTC

   We're investigating elevated error rates affecting the LaunchDarkly web application and API. Some requests may fail or time out intermittently, including custom role management. We'll share an update as we learn more.

2. identified 2026-10-02 17:29 UTC

   Identified. We've identified the cause of the elevated error rates and are working on a fix. Customers may still be unable to list, search, or assign custom roles; existing roles continue to be enforced. Most other features are operating normally, though some requests may fail...

3. monitoring 2026-10-03 01:26 UTC

   Monitoring. We've applied a fix and error rates have returned to normal, including custom role listing, search, and assignment. We're continuing to monitor while we complete recovery work.

4. resolved 2026-10-03 09:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Server-side streaming API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-26 19:45 UTC

   Server-side streaming requests experienced elevated error rates between approximately 12:00 p.m. and 12:12 p.m. PDT, and some SDKs establishing new streaming connections may have been unable to connect. Polling request error rates remained below 1% throughout the incident. No...

2. resolved 2026-08-26 20:00 UTC

   This incident has been resolved. Between 12:00 and 12:12 PM PDT on August 26, server-side SDKs establishing new streaming connections experienced elevated error rates. Existing streaming connections were not affected, and polling requests continued to be served with error rates...

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-24 12:20 UTC

   Emails sent by LaunchDarkly — including sign-up verification, password reset, teammate invitation, and workflow notification emails — are currently failing to deliver due to an authentication issue with an upstream email delivery provider. We have identified the cause and are...

2. resolved 2026-08-24 13:36 UTC

   Email delivery has been restored as of 2:32 PM UTC. Sign-up verification, password reset, teammate invitation, and notification emails are sending normally again. We are re-sending sign-up verification and password reset emails that failed to deliver during the incident window...

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Polling API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-17 10:36 UTC

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

2. monitoring 2026-08-17 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. resolved 2026-08-17 16:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Client-side streaming API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-08-14 14:47 UTC

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

2. monitoring 2026-08-14 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. resolved 2026-08-14 16:47 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: SDKs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 19:29 UTC

   We are investigating elevated HTTP 500 errors affecting some server-side SDK streaming connections in our US commercial environment. Affected applications may fail to establish or may intermittently lose their streaming connection to LaunchDarkly.

2. investigating 2026-08-07 19:56 UTC

   We released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.

3. investigating 2026-08-07 20:12 UTC

   We are continuing to investigate this issue.

4. resolved 2026-08-07 20:15 UTC

   SDKs restored to operational

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: OpenTelemetry (Logs, Traces, Metrics)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 17:44 UTC

   All customers are experiencing missing Observability Traces starting July 30th at 5:16pm PT. We are investigating and will provide updates as they become available. Trace data is not lost and we are working to recover it.

2. identified 2026-07-31 17:59 UTC

   Customers are experiencing missing Observability Traces ingested from July 30th 5:16pm until July 31st 10:59am PT. Observability Logs / Metrics are unaffected. We have identified the issue and are continuing our work to recover the missing Traces data.

3. monitoring 2026-07-31 21:58 UTC

   The issue with Observability Traces has been identified and a fix has been implemented. We have recovered most trace data that was missing from July 30th 5:16pm to July 31st 10:59am PT. We will resolve the incident once we fully complete data recovery (expected to complete by...

4. resolved 2026-07-31 22:54 UTC

   The issue with Observability Traces has been resolved. Missing trace data has been recovered.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Observability Data Ingest (Sessions, Errors)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-28 19:24 UTC

   Customers are experiencing delayed session replay and error ingest as of 11:03am PT. We have identified the issue and are continuing our work to resolve it. Data loss is not expected.

2. monitoring 2026-07-28 19:41 UTC

   The issue with session replay and error ingest has been identified and a fix has been implemented. We expect to catch up on all backlogged data ingest in ~15 minutes. No data has been lost.

3. resolved 2026-07-28 20:04 UTC

   The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-26 18:32 UTC

   Between 11:32 and 11:48 PT, customers experienced increased latency and elevated error rates on API endpoints. Latency and error rates have returned to normal, and the incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications, Feature workflows, Audit log, Experiment management, Past experiment iterations, Authentication, Context processing, Rollout management, Config management, Frontend, Flag targeting, Data Export, Integrations and webhooks, Metrics, Rollout results processing, Query API, Graphs, Flag usage metrics, Experiment results processing, Expiring Contexts Targets, Web app (app.launchdarkly.com), Segment management, Rollout results analysis, Observability Data Ingest (Sessions, Errors), Playgrounds and offline evaluations, Experiment results analysis, Progressive rollouts, OpenTelemetry (Logs, Traces, Metrics), AI insights, Release pipelines, Warehouse native experimentation, Account management

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 17:10 UTC

   The LaunchDarkly web application (app.launchdarkly.com) was unavailable and is actively recovering at the moment. The Flag Delivery network was also impacted, causing an elevated failure rate with retrieving flag values. Customers using client-side or server-side SDKs should...

2. identified 2026-07-10 17:12 UTC

   We have identified the root cause and are implementing a fix.

3. identified 2026-07-10 17:40 UTC

   The web application availability has recovered. Flag delivery and event ingestion continue to be impacted and are actively recovering. Our engineering team continues to work on remediation.

4. monitoring 2026-07-10 17:54 UTC

   Production service impact has been restored. However, customers might need to restart their applications to fully reconnect to LaunchDarkly's services. Our engineering team is working on guidance that can be provided to customers.

5. resolved 2026-07-10 18:19 UTC

   All service availability has been fully restored. Customers using server-side SDKs might need to restart their applications to re-enable the SDKs' connection to LaunchDarkly. Customers using the Relay Proxy may also need to restart their Relay Proxy; in this case, the Relay...

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications, Feature workflows, Audit log, Experiment management, Past experiment iterations, Authentication, Context processing, Rollout management, Config management, Frontend, Flag targeting, Data Export, Integrations and webhooks, Metrics, Rollout results processing, Query API, Graphs, Flag usage metrics, Experiment results processing, Expiring Contexts Targets, Web app (app.launchdarkly.com), Segment management, Rollout results analysis, Observability Data Ingest (Sessions, Errors), Playgrounds and offline evaluations, Experiment results analysis, Progressive rollouts, OpenTelemetry (Logs, Traces, Metrics), AI insights, Release pipelines, Warehouse native experimentation

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 16:16 UTC

   We are currently investigating this issue

2. investigating 2026-07-10 16:17 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-10 16:26 UTC

   The issue has been identified and a fix has been implemented

4. identified 2026-07-10 16:47 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-07-10 17:43 UTC

   We are continuing to work on a fix for this issue.

6. resolved 2026-07-10 17:48 UTC

   LaunchDarkly UI has recovered. We will continue to monitor Flag Delivery and event ingest here: https://status.launchdarkly.com/incidents/chywwz01ptb0.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: SDKs

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 16:00 UTC

   We are investigating continued impact to customers' mobile and server SDK caused by the previous incident (https://status.launchdarkly.com/incidents/chywwz01ptb0). If customers are receiving SDK or Relay Proxy 401s please re-establish connections.

2. monitoring 2026-07-10 20:18 UTC

   Our Flag Delivery services have recovered and we're observing an increase in customer traffic successfully reestablish connections to our streaming services. Customers who continue to encounter 401 connection errors in their SDKs or Relay Proxy instances are advised to restart...

3. monitoring 2026-07-10 23:32 UTC

   Customers continue to successfully reestablish connections to our streaming services. We recommend reviewing your application logs for the incident window. Affected SDKs emit messages—varying by language—that contain any of the following: "giving up permanently," "Invalid SDK...

4. monitoring 2026-07-11 02:00 UTC

   We are continuing to monitor for any further issues, see our previous update for recovery steps.

5. monitoring 2026-07-13 18:08 UTC

   All LaunchDarkly services are operational, though some customers need to take action to restore their connections to our Flag Delivery Network. Customers continue to successfully reestablish connections by completing the action guidance below and we continue to support customers...

6. resolved 2026-07-29 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment management

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 18:03 UTC

   We are currently investigating an issue where experiments using frequentist analysis cannot be saved or started.

2. identified 2026-07-08 18:12 UTC

   We have identified the issue and are working towards releasing a fix.

3. monitoring 2026-07-08 18:51 UTC

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

4. resolved 2026-07-08 19:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Data Export, Rollout results processing, Experiment results processing, Rollout results analysis, Experiment results analysis, Warehouse native experimentation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-07 15:10 UTC

   Event ingestion is operating normally. Experimentation results, Guarded Rollouts, and in-product data charts were delayed ~5 min between 7:13–7:53 AM PT. No data was lost. We apologize for any inconvenience.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Server-side streaming API, Authentication, Web app (app.launchdarkly.com)

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-06 20:30 UTC

   At 13:21 Pacific Time, we experienced a high volume of error alerts affecting users' ability to interact with the LaunchDarkly application including logging in and UI / API responsiveness. We quickly identified the root cause relating to flag delivery. We are expecting errors...

2. investigating 2026-07-06 20:45 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-06 21:09 UTC

   We have rolled out a fix and error rates are returning to normal

4. resolved 2026-07-06 21:21 UTC

   All error rates have normalized.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-06 14:33 UTC

   Some customers are not receiving account verification emails. Our team is actively working to mitigate this issue.

2. monitoring 2026-07-06 14:45 UTC

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

3. resolved 2026-07-06 15:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Metrics, Flag usage metrics, Experiment results processing, Rollout results analysis, AI insights

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-03 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...

2. monitoring 2026-07-03 15:13 UTC

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

3. resolved 2026-07-03 16:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Docs (launchdarkly.com/docs), Website (launchdarkly.com)

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-17 19:43 UTC

   LaunchDarkly web application and flag delivery unaffected, but documentation and LaunchDarkly.com are unavailable for some users. A fix is on the way.

2. monitoring 2026-06-17 19:59 UTC

   A fix has been implemented and monitoring the results.

3. monitoring 2026-06-17 23:56 UTC

   Incident seems to be resolved for the majority of users, however, we are continuing to see some issues for in the San Jose and Los Angeles region. We're working to remediate for these regions.

4. monitoring 2026-06-18 01:23 UTC

   We've identified the source of the problem for areas that were still seeing issues with the LaunchDarkly.com and docs and have a solution in place. We are now monitoring to ensure everything is resolved.

5. resolved 2026-06-18 01:30 UTC

   We're now seeing restored access in the affected regions.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: OpenTelemetry (Logs, Traces, Metrics)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-15 17:02 UTC

   Some customers are experiencing delayed Observability data ingest for OpenTelemetry data. We have identified the issue and are continuing our work to resolve it. Observability signals (errors / logs / traces / OTel metrics) are currently delayed by ~6 minutes on average. Data...

2. monitoring 2026-06-15 17:33 UTC

   The issue with Observability data ingest for OpenTelemetry data has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved. Observability signals (errors / logs...

3. resolved 2026-06-15 17:38 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment management, Authentication, Flag targeting, Web app (app.launchdarkly.com), Progressive rollouts

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-12 04:23 UTC

   We identified a brief period of elevated errors affecting some LaunchDarkly application requests between 7:30-7:37pm PT. The issue has recovered, and we are continuing to monitor.

2. resolved 2026-06-12 04:58 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Data Export, Metrics, Rollout results processing, Flag usage metrics, Experiment results processing, Rollout results analysis, Experiment results analysis, AI insights, Warehouse native experimentation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-08 20:46 UTC

   We are currently experiencing delays in event ingestion impacting multiple product areas starting at 12:40pm PT. We have identified the issue and are working on a fix. No data has been lost.

2. monitoring 2026-06-08 21:24 UTC

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

3. monitoring 2026-06-09 02:03 UTC

   We are monitoring the status of our services.

4. monitoring 2026-06-09 02:23 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-06-09 12:08 UTC

   We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.

6. monitoring 2026-06-10 18:54 UTC

   We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.

7. monitoring 2026-06-11 01:31 UTC

   We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

8. monitoring 2026-06-11 04:07 UTC

   We are continuing to monitor for any further issues.

9. monitoring 2026-06-11 04:07 UTC

   We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

10. monitoring 2026-06-11 04:12 UTC

    We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

11. monitoring 2026-06-11 05:14 UTC

    We have made partial progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are...

12. monitoring 2026-06-11 15:37 UTC

    We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are...

13. monitoring 2026-06-12 22:15 UTC

    We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are...

14. resolved 2026-06-13 13:52 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Flag targeting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 19:31 UTC

   Currently investigating an issue causing the flag dashboard to fail to load.

2. identified 2026-06-03 19:54 UTC

   The issue has been identified and a fix is in progress.

3. monitoring 2026-06-03 20:06 UTC

   A fix has been implemented and were monitoring the results

4. resolved 2026-06-03 20:26 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 18:40 UTC

   We are experiencing issues with sending Slack notifications for segment approvals. Email and in-app notifications still work as expected. We are working on restoring this functionality as soon as possible.

2. monitoring 2026-05-22 19:33 UTC

   A fix has been implemented and we are monitoring notifications.

3. resolved 2026-05-22 19:41 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Rollout results processing, Experiment results processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-19 14:49 UTC

   We are currently experiencing delays in event ingestion, which is impacting Experimentation results and Guarded Rollouts. No data has been lost — all results and events are intact and will be fully accessible once a fix has been deployed. We have identified the root cause and a...

2. resolved 2026-05-19 14:54 UTC

   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. Results were delayed from 6:58am PDT to 7:52am PDT

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Observability Data Ingest (Sessions, Errors)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-16 00:03 UTC

   We are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed — no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI.

2. identified 2026-05-16 00:14 UTC

   We have identified the issue and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.

3. resolved 2026-05-16 01:13 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Server-side streaming API

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 03:58 UTC

   We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.

2. identified 2026-05-06 04:00 UTC

   We're identified an infrastructure issue causing elevated error rates and are working on a fix.

3. resolved 2026-05-06 04:26 UTC

   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.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment results processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 19:47 UTC

   We are currently investigating delays in experiment and multi-armed bandit results. Data is currently delayed by 1-2 hours. No data loss is expected.

2. identified 2026-05-04 19:50 UTC

   We have identified the issue and are continuing our work to resolve it.

3. monitoring 2026-05-04 20:19 UTC

   We have implemented a fix and are catching up on backlogged data. We estimate that we will be fully caught up in about 1 hour.

4. resolved 2026-05-04 20:25 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Server-side streaming API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 10:14 UTC

   We are investigating elevated error rates for streaming initialization in the Europe region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.

2. identified 2026-05-04 12:51 UTC

   We're identified an infrastructure issue causing elevated error rates and are working on a fix.

3. identified 2026-05-04 14:30 UTC

   We're continuing to address the root cause of the elevated error rate. Server SDKs may require additional time to initialize while requests are retried.

4. monitoring 2026-05-04 15:47 UTC

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

5. resolved 2026-05-04 16:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment results processing, Warehouse native experimentation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-02 12:55 UTC

   We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.

2. identified 2026-05-02 13:17 UTC

   We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.

3. monitoring 2026-05-02 13:51 UTC

   We have implemented a fix and are catching up on backlogged experimentation results and data export. We estimate that we will be fully caught up in about 8 hours.

4. resolved 2026-05-02 19:15 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-01 02:52 UTC

   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.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Data Export

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 11:14 UTC

   We are investigating a delay with streaming data export delivery. No data is lost, but customers using streaming data export may notice a multi-minute lag in receiving data.

2. monitoring 2026-04-30 11:45 UTC

   We've identified latency in Pub/Sub export that were causing streaming data export delays that has since resolved. We're catching up on the export backlog now.

3. resolved 2026-04-30 11:58 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-29 23:45 UTC

   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.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment results processing, Experiment results analysis

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-29 20:19 UTC

   We are aware of an issue affecting some customers that may result in sample ratio mismatches (SRMs) or empty experiment results if flag variations are edited between experiment iterations.

2. identified 2026-04-29 20:49 UTC

   We've identified the issue and are implementing a fix for this behavior.

3. monitoring 2026-04-30 00:04 UTC

   We've released a fix to prevent this issue in new experiments and iterations. We're working to resolve this issue for experiment data recently processed.

4. resolved 2026-05-01 00:09 UTC

   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.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 18:34 UTC

   We are currently investigating an issue prevent Observability alert notifications from being delivered.

2. identified 2026-04-28 18:38 UTC

   We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational.

3. monitoring 2026-04-28 19:10 UTC

   A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.

4. resolved 2026-04-28 19:25 UTC

   Observability alerts are functioning and delayed alerts have been redelivered.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-27 15:39 UTC

   We are investigating an issue causing under-reporting of customer metrics in the EU region.

2. identified 2026-04-27 15:45 UTC

   We've identified that metrics ingest was delayed between 11:11 - 11:27am ET. No metric data has been lost. We're working on catching up on the delayed data.

3. monitoring 2026-04-27 16:43 UTC

   We're catching up on backlogged metric data in EU and are monitoring progress. No metric data has been lost.

4. resolved 2026-04-27 17:37 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-23 19:00 UTC

   We've addressed an issue that prevented warehouse data export from 12pm to 6pm PT on April 23. All missing data has been retroactively pushed to customer warehouses.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Docs (launchdarkly.com/docs)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-20 22:04 UTC

   We are currently investigating this issue.

2. investigating 2026-04-20 22:13 UTC

   We have linked this issue with an outage on our doc provider's side.

3. identified 2026-04-20 22:13 UTC

   The issue has been identified and a fix is being implemented.

4. resolved 2026-04-20 22:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Emails and notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 21:27 UTC

   We are currently investigating an issue where observability alerts are not delivering for Slack notifications to all channels. DM alerts are still functional.

2. identified 2026-04-20 22:01 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-04-20 23:44 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-10 04:30 UTC

   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...

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Observability Data Ingest (Sessions, Errors)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-06 17:58 UTC

   We are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed — no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI. We have...

2. identified 2026-04-06 18:15 UTC

   We have identified the cause of the delayed Session Replay and Error event processing and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.

3. monitoring 2026-04-06 18:40 UTC

   The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.

4. resolved 2026-04-06 19:02 UTC

   The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-03-19 16:58 UTC

   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...

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Past experiment iterations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-18 02:07 UTC

   We are aware of an issue affecting experiment reporting data for a subset of accounts. Affected users may see incomplete data for some experiment iterations in the UI.

2. identified 2026-03-18 02:08 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-03-18 04:17 UTC

   We have implemented a mitigation that restores data availability for all current experiment iterations. Affected accounts should now see up-to-date reporting and exposure data in the UI. Our team continues to work on restoring data for previously affected experiment iterations....

4. identified 2026-03-18 22:37 UTC

   Our team continues to work on restoring data for previously affected experiment iterations. We will provide a further update once full historical data recovery is complete.

5. identified 2026-03-19 04:52 UTC

   Our team continues to work on restoring data for previously affected experiment iterations. Complete data restoration expected by tomorrow.

6. resolved 2026-03-20 00:29 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment results processing, Warehouse native experimentation

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-10 22:59 UTC

   Event processing is currently delayed for and will show stale data for several product areas, including: - Autogenerated metric creation - Data Export - Experimentation No data has been lost.

2. monitoring 2026-03-10 23:38 UTC

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

3. monitoring 2026-03-10 23:42 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-03-11 04:07 UTC

   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.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-03 20:40 UTC

   We're investigating reports of inaccurate usage reporting for some Observability products.

2. identified 2026-03-03 21:15 UTC

   We've identified the root cause affecting the Observability "Errors" usage for some customers and are working to correct it.

3. resolved 2026-03-04 01:13 UTC

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

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Authentication, Web app (app.launchdarkly.com)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-26 15:43 UTC

   Some customers are experiencing issues with accessing the web app and authentication. We are investigating and will provide updates as they become available.

2. identified 2026-02-26 16:17 UTC

   Some customers are experiencing issues with accessing the web app and authentication. Some customers may see a low number of errors with flag evaluation, as well, but generally our Flag Delivery Network is functional. We have identified the issue and are continuing our work to...

3. monitoring 2026-02-26 16:42 UTC

   The issue with our application and authentication has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.

4. monitoring 2026-02-26 17:04 UTC

   The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.

5. resolved 2026-02-26 17:06 UTC

   The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: OpenTelemetry (Logs, Traces, Metrics)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-20 22:02 UTC

   Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.

2. identified 2026-02-20 22:12 UTC

   We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.

3. monitoring 2026-02-20 22:13 UTC

   Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.

4. resolved 2026-02-20 23:04 UTC

   Ingest performance has remained stable following mitigation. We are no longer observing impact.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Observability Data Ingest (Sessions, Errors)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-19 15:39 UTC

   Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.

2. identified 2026-02-19 15:54 UTC

   We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.

3. resolved 2026-02-19 16:09 UTC

   We've caught up on the session/error data backlog.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.

Affected: Experiment results analysis

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 00:30 UTC

   We are investigating an issue where certain experiment iterations are receiving incorrectly attributed data.

2. identified 2026-02-13 01:32 UTC

   The team has identified the root cause and is working on a fix.

3. identified 2026-02-13 02:38 UTC

   We have fixed the data attribution issues where certain experiment iterations are receiving incorrectly attributed data for any new experiments that are created. We are fixing the data attribution error for active experiments.

4. resolved 2026-02-13 03:39 UTC

   We have fixed the data attribution issues where running experiment iterations were receiving incorrectly attributed data. This incident is now resolved and results for active experiments are now accurate.

Excerpts are shortened. Read the full incident on LaunchDarkly's status page.