- Detected by Pingoru
- Jul 31, 2026, 05:44 PM UTC
- Resolved
- Jul 31, 2026, 10:54 PM UTC
- Duration
- 5h 10m
Affected: OpenTelemetry (Logs, Traces, Metrics)
Timeline · 4 updates
-
investigating Jul 31, 2026, 05:44 PM 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.
-
identified Jul 31, 2026, 05:59 PM 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.
-
monitoring Jul 31, 2026, 09:58 PM 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 5pm PT).
-
resolved Jul 31, 2026, 10:54 PM UTC
The issue with Observability Traces has been resolved. Missing trace data has been recovered.
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2026, 07:24 PM UTC
- Resolved
- Jul 28, 2026, 08:04 PM UTC
- Duration
- 40m
Affected: Observability Data Ingest (Sessions, Errors)
Timeline · 3 updates
-
identified Jul 28, 2026, 07:24 PM 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.
-
monitoring Jul 28, 2026, 07:41 PM 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.
-
resolved Jul 28, 2026, 08:04 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 26, 2026, 06:32 PM UTC
- Resolved
- Jul 26, 2026, 06:32 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 26, 2026, 07:09 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 05:40 PM UTC
- Resolved
- Jul 10, 2026, 06:19 PM UTC
- Duration
- 39m
Affected: Emails and notificationsFeature workflowsAudit logExperiment managementPast experiment iterationsAuthenticationContext processingRollout managementConfig managementFrontendFlag targetingData ExportIntegrations and webhooksMetricsRollout results processingQuery APIFlag usage metricsExperiment results processingExpiring Contexts TargetsWeb app (app.launchdarkly.com)Segment managementRollout results analysisObservability Data Ingest (Sessions, Errors)Experiment results analysisProgressive rolloutsOpenTelemetry (Logs, Traces, Metrics)Release pipelinesWarehouse native experimentationAccount managementGraphsPlaygrounds and offline evaluationsAI insights
Timeline · 5 updates
-
investigating Jul 10, 2026, 05:10 PM 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 continue to see the last known flag values if a local cache exists, or fall back to in-code values. Customers using our Relay Proxy should continue to see last known flag values if a local cache exists. Customers using our Edge SDKs should continue to see last known flag values. Some event data loss may have occurred.
-
identified Jul 10, 2026, 05:12 PM UTC
We have identified the root cause and are implementing a fix.
-
identified Jul 10, 2026, 05:40 PM 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.
-
monitoring Jul 10, 2026, 05:54 PM 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.
-
resolved Jul 10, 2026, 06:19 PM 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 Proxy should be restarted before restarting their applications that connect to it. To determine if an application needs to be restarted, customers can look at their application logs. Affected SDKs will emit (depending on language) logs containing one of "giving up permanently", "Invalid SDK key", "unauthorized", or "not authorized", or "401". Services which emitted logs such as these before 9:13AM PT may be unable to receive flag updates and will be unable to send events to LaunchDarkly until they are restarted.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 04:16 PM UTC
- Resolved
- Jul 10, 2026, 05:48 PM UTC
- Duration
- 1h 31m
Affected: Emails and notificationsFeature workflowsAudit logExperiment managementPast experiment iterationsAuthenticationContext processingRollout managementConfig managementFrontendFlag targetingData ExportIntegrations and webhooksMetricsRollout results processingQuery APIFlag usage metricsExperiment results processingExpiring Contexts TargetsWeb app (app.launchdarkly.com)Segment managementRollout results analysisObservability Data Ingest (Sessions, Errors)Experiment results analysisProgressive rolloutsOpenTelemetry (Logs, Traces, Metrics)Release pipelinesWarehouse native experimentationGraphsPlaygrounds and offline evaluationsAI insights
Timeline · 6 updates
-
investigating Jul 10, 2026, 04:16 PM UTC
We are currently investigating this issue
-
investigating Jul 10, 2026, 04:17 PM UTC
We are continuing to investigate this issue.
-
identified Jul 10, 2026, 04:26 PM UTC
The issue has been identified and a fix has been implemented
-
identified Jul 10, 2026, 04:47 PM UTC
We are continuing to work on a fix for this issue.
-
identified Jul 10, 2026, 05:43 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Jul 10, 2026, 05:48 PM UTC
LaunchDarkly UI has recovered. We will continue to monitor Flag Delivery and event ingest here: https://status.launchdarkly.com/incidents/chywwz01ptb0.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 04:00 PM UTC
- Resolved
- Jul 29, 2026, 06:15 PM UTC
- Duration
- 19d 2h
Affected: SDKs
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 06:03 PM UTC
- Resolved
- Jul 08, 2026, 07:41 PM UTC
- Duration
- 1h 38m
Affected: Experiment management
Timeline · 4 updates
-
investigating Jul 08, 2026, 06:03 PM UTC
We are currently investigating an issue where experiments using frequentist analysis cannot be saved or started.
-
identified Jul 08, 2026, 06:12 PM UTC
We have identified the issue and are working towards releasing a fix.
-
monitoring Jul 08, 2026, 06:51 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 08, 2026, 07:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 03:10 PM UTC
- Resolved
- Jul 07, 2026, 03:10 PM UTC
- Duration
- —
Affected: Data ExportRollout results processingExperiment results processingRollout results analysisExperiment results analysisWarehouse native experimentation
Timeline · 1 update
-
resolved Jul 07, 2026, 03:10 PM 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.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 08:30 PM UTC
- Resolved
- Jul 06, 2026, 09:21 PM UTC
- Duration
- 51m
Affected: Server-side streaming APIFeature workflowsAuthenticationFlag targetingWeb app (app.launchdarkly.com)
Timeline · 4 updates
-
investigating Jul 06, 2026, 08:52 PM UTC
At 13:21 Pacific Time, we experienced a high volume of error alerts. We quickly identified a flag change related to flag delivery. We are expecting errors decreasing now.
-
investigating Jul 06, 2026, 09:08 PM UTC
We are continuing to investigate this issue.
-
monitoring Jul 06, 2026, 09:09 PM UTC
We have rolled out a fix and error rates are returning to normal
-
resolved Jul 06, 2026, 09:21 PM UTC
All error rates have normalized.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 02:33 PM UTC
- Resolved
- Jul 06, 2026, 03:52 PM UTC
- Duration
- 1h 19m
Affected: Emails and notifications
Timeline · 3 updates
-
investigating Jul 06, 2026, 02:33 PM UTC
Some customers are not receiving account verification emails. Our team is actively working to mitigate this issue.
-
monitoring Jul 06, 2026, 02:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 06, 2026, 03:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 02:29 PM UTC
- Resolved
- Jul 03, 2026, 04:06 PM UTC
- Duration
- 1h 37m
Affected: MetricsFlag usage metricsExperiment results processingRollout results analysisAI insights
Timeline · 3 updates
-
investigating Jul 03, 2026, 02:29 PM 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.
-
monitoring Jul 03, 2026, 03:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 03, 2026, 04:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 07:43 PM UTC
- Resolved
- Jun 18, 2026, 01:30 AM UTC
- Duration
- 5h 46m
Affected: Docs (launchdarkly.com/docs)Website (launchdarkly.com)
Timeline · 5 updates
-
identified Jun 17, 2026, 07:43 PM UTC
LaunchDarkly web application and flag delivery unaffected, but documentation and LaunchDarkly.com are unavailable for some users. A fix is on the way.
-
monitoring Jun 17, 2026, 07:59 PM UTC
A fix has been implemented and monitoring the results.
-
monitoring Jun 17, 2026, 11:56 PM 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.
-
monitoring Jun 18, 2026, 01:23 AM 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.
-
resolved Jun 18, 2026, 01:30 AM UTC
We're now seeing restored access in the affected regions.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 05:02 PM UTC
- Resolved
- Jun 15, 2026, 05:38 PM UTC
- Duration
- 36m
Affected: OpenTelemetry (Logs, Traces, Metrics)
Timeline · 3 updates
-
identified Jun 15, 2026, 05:26 PM 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 ingest delays began at 10:02am and are improving as of 10:16am PT.
-
monitoring Jun 15, 2026, 05:33 PM 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 / traces / OTel metrics) are currently delayed by <1 minutes on average.
-
resolved Jun 15, 2026, 05:38 PM UTC
The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 04:23 AM UTC
- Resolved
- Jun 12, 2026, 04:58 AM UTC
- Duration
- 35m
Affected: Experiment managementAuthenticationFlag targetingWeb app (app.launchdarkly.com)Progressive rollouts
Timeline · 2 updates
-
monitoring Jun 12, 2026, 04:23 AM 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.
-
resolved Jun 12, 2026, 04:58 AM UTC
Monitoring has confirmed no further impact outside of the initially reported 7:30-7:37pm PT timeframe
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 12:08 PM UTC
- Resolved
- Jun 13, 2026, 01:52 PM UTC
- Duration
- 4d 1h
Affected: Data ExportMetricsRollout results processingFlag usage metricsExperiment results processingRollout results analysisExperiment results analysisWarehouse native experimentationAI insights
Timeline · 14 updates
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 07:31 PM UTC
- Resolved
- Jun 03, 2026, 08:26 PM UTC
- Duration
- 55m
Affected: Flag targeting
Timeline · 4 updates
-
investigating Jun 03, 2026, 07:31 PM UTC
Currently investigating an issue causing the flag dashboard to fail to load.
-
identified Jun 03, 2026, 07:54 PM UTC
The issue has been identified and a fix is in progress.
-
monitoring Jun 03, 2026, 08:06 PM UTC
A fix has been implemented and were monitoring the results
-
resolved Jun 03, 2026, 08:26 PM UTC
The incident has been resolved and the flag dashboard is successfully loading.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 06:40 PM UTC
- Resolved
- May 22, 2026, 07:41 PM UTC
- Duration
- 1h 1m
Affected: Emails and notifications
Timeline · 3 updates
-
investigating May 22, 2026, 06:40 PM 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.
-
monitoring May 22, 2026, 07:33 PM UTC
A fix has been implemented and we are monitoring notifications.
-
resolved May 22, 2026, 07:41 PM UTC
We have confirmed Slack notifications are now coming through for segment approvals again.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:49 PM UTC
- Resolved
- May 19, 2026, 02:54 PM UTC
- Duration
- 5m
Affected: Rollout results processingExperiment results processing
Timeline · 2 updates
-
identified May 19, 2026, 02:49 PM 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 fix is being released now.
-
resolved May 19, 2026, 02:54 PM 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.
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 12:03 AM UTC
- Resolved
- May 16, 2026, 01:13 AM UTC
- Duration
- 1h 9m
Affected: Observability Data Ingest (Sessions, Errors)
Timeline · 3 updates
-
investigating May 16, 2026, 12:03 AM 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.
-
identified May 16, 2026, 12:14 AM 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.
-
resolved May 16, 2026, 01:13 AM UTC
All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 03:58 AM UTC
- Resolved
- May 06, 2026, 04:26 AM UTC
- Duration
- 27m
Affected: Server-side streaming API
Timeline · 3 updates
-
investigating May 06, 2026, 03:58 AM UTC
We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs in the APAC region with may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
-
identified May 06, 2026, 04:00 AM UTC
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
-
resolved May 06, 2026, 04:26 AM 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.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 07:47 PM UTC
- Resolved
- May 04, 2026, 08:25 PM UTC
- Duration
- 37m
Affected: Experiment results processing
Timeline · 4 updates
-
investigating May 04, 2026, 07:47 PM 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.
-
identified May 04, 2026, 07:50 PM UTC
We have identified the issue and are continuing our work to resolve it.
-
monitoring May 04, 2026, 08:19 PM 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.
-
resolved May 04, 2026, 08:25 PM UTC
All experiment and multi-armed bandit result data is caught up. No data was lost.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 10:14 AM UTC
- Resolved
- May 04, 2026, 04:23 PM UTC
- Duration
- 6h 8m
Affected: Server-side streaming API
Timeline · 5 updates
-
investigating May 04, 2026, 12:28 PM 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.
-
identified May 04, 2026, 12:51 PM UTC
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
-
identified May 04, 2026, 02:30 PM 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.
-
monitoring May 04, 2026, 03:47 PM 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.
-
resolved May 04, 2026, 04:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 02, 2026, 12:55 PM UTC
- Resolved
- May 02, 2026, 07:15 PM UTC
- Duration
- 6h 20m
Affected: Experiment results processingWarehouse native experimentation
Timeline · 4 updates
-
investigating May 02, 2026, 12:55 PM UTC
We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.
-
identified May 02, 2026, 01:17 PM UTC
We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.
-
monitoring May 02, 2026, 01:51 PM 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.
-
resolved May 02, 2026, 07:15 PM UTC
Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 04:06 AM UTC
- Resolved
- May 01, 2026, 02:52 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 01, 2026, 04:06 AM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 11:14 AM UTC
- Resolved
- Apr 30, 2026, 11:58 AM UTC
- Duration
- 43m
Affected: Data Export
Timeline · 3 updates
-
investigating Apr 30, 2026, 11:14 AM 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.
-
monitoring Apr 30, 2026, 11:45 AM 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.
-
resolved Apr 30, 2026, 11:58 AM UTC
We've caught up on the streaming data export backlog.
Read the full incident report →
