- Detected by Pingoru
- Feb 26, 2026, 03:43 PM UTC
- Resolved
- Feb 26, 2026, 05:06 PM UTC
- Duration
- 1h 22m
Affected: AuthenticationWeb app (app.launchdarkly.com)
Timeline · 5 updates
-
investigating Feb 26, 2026, 03:43 PM UTC
Some customers are experiencing issues with accessing the web app and authentication. We are investigating and will provide updates as they become available.
-
identified Feb 26, 2026, 04:17 PM 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 resolve it.
-
monitoring Feb 26, 2026, 04:42 PM 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.
-
monitoring Feb 26, 2026, 05:04 PM UTC
The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
-
resolved Feb 26, 2026, 05:06 PM UTC
The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 10:02 PM UTC
- Resolved
- Feb 20, 2026, 11:04 PM UTC
- Duration
- 1h 1m
Affected: OpenTelemetry (Logs, Traces, Metrics)
Timeline · 4 updates
-
investigating Feb 20, 2026, 10:02 PM 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.
-
identified Feb 20, 2026, 10:12 PM 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.
-
monitoring Feb 20, 2026, 10:13 PM UTC
Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.
-
resolved Feb 20, 2026, 11:04 PM UTC
Ingest performance has remained stable following mitigation. We are no longer observing impact.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 03:39 PM UTC
- Resolved
- Feb 19, 2026, 04:09 PM UTC
- Duration
- 29m
Affected: Observability Data Ingest (Sessions, Errors)
Timeline · 3 updates
-
investigating Feb 19, 2026, 03:39 PM UTC
Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.
-
identified Feb 19, 2026, 03:54 PM 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.
-
resolved Feb 19, 2026, 04:09 PM UTC
We've caught up on the session/error data backlog.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 11:30 PM UTC
- Resolved
- Feb 13, 2026, 03:39 AM UTC
- Duration
- 4h 8m
Affected: Experiment results analysis
Timeline · 4 updates
-
investigating Feb 13, 2026, 01:31 AM UTC
We are investigating an issue where certain experiment iterations are receiving incorrectly attributed data.
-
identified Feb 13, 2026, 01:32 AM UTC
The team has identified the root cause and is working on a fix.
-
identified Feb 13, 2026, 02:38 AM 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.
-
resolved Feb 13, 2026, 03:39 AM 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.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 01:03 PM UTC
- Resolved
- Feb 12, 2026, 03:53 AM UTC
- Duration
- 14h 50m
Affected: OpenTelemetry (Logs, Traces, Metrics)
Timeline · 2 updates
-
investigating Feb 12, 2026, 03:50 AM UTC
We are currently investigating an issue affecting OTel telemetry ingestion in LaunchDarkly Observability. Some telemetry data may not be processed as expected. Our team is actively working to identify the root cause and mitigate impact.
-
resolved Feb 12, 2026, 03:53 AM UTC
This incident has been resolved. Telemetry data was dropped between 5:03 PM and 7:30 PM PT. All systems are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 07:30 AM UTC
- Resolved
- Feb 10, 2026, 09:01 AM UTC
- Duration
- 1h 30m
Affected: Observability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)
Timeline · 2 updates
-
investigating Feb 10, 2026, 08:42 AM UTC
Some customers using LaunchDarkly Observability with AWS CloudWatch Metric Stream and/or CloudWatch Firehose log export may experience delayed ingestion of metrics/logs into Observability. The impact is limited to Observability data ingestion and related dashboards/alerts.
-
resolved Feb 10, 2026, 09:01 AM UTC
This issue has been resolved. Observability ingestion from AWS CloudWatch Metric Streams and CloudWatch Firehose log export has returned to normal. Data sent during the incident window may not have been ingested, and customers may see gaps in metrics or logs for that period.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 11:55 AM UTC
- Resolved
- Feb 06, 2026, 12:44 PM UTC
- Duration
- 49m
Affected: Web app (app.launchdarkly.com)
Timeline · 2 updates
-
investigating Feb 06, 2026, 11:55 AM UTC
We are investigating an issue where a small number of customers may experience errors when accessing the LaunchDarkly UI and API. Feature flag delivery is not impacted. We will provide updates as the investigation continues.
-
resolved Feb 06, 2026, 12:44 PM UTC
Customers are seeing expected behavior when accessing the LaunchDarkly UI and API.
Read the full incident report →
- Detected by Pingoru
- Jan 31, 2026, 10:02 AM UTC
- Resolved
- Jan 31, 2026, 12:20 PM UTC
- Duration
- 2h 18m
Affected: Context processingFlag usage metricsObservability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)
Timeline · 4 updates
-
investigating Jan 31, 2026, 10:02 AM UTC
All customers are experiencing data ingestion delays with the following: - Observability sessions and errors - Opentelemetry logs, traces, and metrics - Flag status - Evaluations - Contexts We are investigating and will provide updates as they become available. No data loss is expected.
-
identified Jan 31, 2026, 10:23 AM UTC
We have identified the issue and are continuing our work to resolve it.
-
monitoring Jan 31, 2026, 11:35 AM UTC
A fix has been implemented and our event processing pipeline for Observability and Opentelemetry are fully caught up. We're continuing to monitor as our event processing pipeline catches up for Flag Status, Evaluations, and Contexts.
-
resolved Jan 31, 2026, 12:20 PM UTC
This incident has been resolved and all data processing pipelines are fully caught up. No data was lost.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 05:54 PM UTC
- Resolved
- Jan 26, 2026, 10:13 PM UTC
- Duration
- 4h 18m
Affected: Authentication
Timeline · 4 updates
-
identified Jan 26, 2026, 05:54 PM UTC
Some customers are experiencing errors when configuring LaunchDarkly with Okta SCIM. We have identified the issue and are continuing our work to resolve it.
-
identified Jan 26, 2026, 07:56 PM UTC
Some customers using Okta SCIM are encountering errors when provisioning and managing LaunchDarkly members. We continue to work on a remediation and have engaged with Okta's support team.
-
monitoring Jan 26, 2026, 08:29 PM UTC
We believe the issue is resolved for all customers. We're continuing to monitor the situation.
-
resolved Jan 26, 2026, 10:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 05:48 PM UTC
- Resolved
- Jan 12, 2026, 07:44 PM UTC
- Duration
- 1h 56m
Affected: Flag targeting
Timeline · 4 updates
-
investigating Jan 12, 2026, 05:48 PM UTC
Customers may experience issues editing JSON flag variation. We are investigating the root cause and will provide updates shortly.
-
identified Jan 12, 2026, 06:49 PM UTC
We've identified a front-end issue that is causing issues editing certain JSON flag variations and are working on a fix.
-
monitoring Jan 12, 2026, 07:16 PM UTC
A fix has been implemented for the issue preventing editing some JSON flag variations.
-
resolved Jan 12, 2026, 07:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 06:46 PM UTC
- Resolved
- Jan 08, 2026, 10:00 PM UTC
- Duration
- 3h 13m
Affected: Rollout results processingRollout results analysis
Timeline · 4 updates
-
identified Jan 08, 2026, 06:46 PM UTC
We are currently experiencing delays with guarded releases event ingestion. We are investigating and will provide updates as they become available.
-
monitoring Jan 08, 2026, 06:57 PM UTC
A fix has been implemented and we are monitoring the results. We expect to catch up on all events within the next 15 minutes, no data loss is expected.
-
monitoring Jan 08, 2026, 07:08 PM UTC
Events are caught up.
-
resolved Jan 08, 2026, 10:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 17, 2025, 06:33 PM UTC
- Resolved
- Dec 17, 2025, 08:51 PM UTC
- Duration
- 2h 17m
Affected: Observability Data Ingest (Sessions, Errors)
Timeline · 4 updates
-
investigating Dec 17, 2025, 06:33 PM UTC
Sessions and errors may be delayed by up to 3 hours. We are investigating the root cause.
-
identified Dec 17, 2025, 07:35 PM UTC
We have identified the cause of the ingest delay and are catching up on the backlogged messages. We expect to be caught up on all delayed sessions and errors in the next hour. Data loss is not expected.
-
monitoring Dec 17, 2025, 08:20 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 17, 2025, 08:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 02:14 PM UTC
- Resolved
- Dec 15, 2025, 04:38 PM UTC
- Duration
- 2h 24m
Affected: Server-side streaming APIFlag targetingClient-side streaming APIPolling API
Timeline · 8 updates
-
investigating Dec 15, 2025, 02:14 PM UTC
We are investigating an increase in SDK error rates affecting a small portion of requests, currently estimated at less than one percent. SDKs will automatically retry these errors, so the primary customer impact is expected to be longer SDK initialization times rather than request failures. We believe the issue is related to an ongoing incident affecting one of our vendors. Our team is actively working to mitigate the impact and will provide additional updates as more information becomes available.
-
investigating Dec 15, 2025, 02:42 PM UTC
We are continuing to investigate this issue.
-
investigating Dec 15, 2025, 03:03 PM UTC
We are also observing a small percentage timeouts when modifying feature flags via our API or UI. We are continuing to investigate this error.
-
investigating Dec 15, 2025, 03:22 PM UTC
We are continuing to investigate this issue.
-
identified Dec 15, 2025, 03:31 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Dec 15, 2025, 03:43 PM UTC
We are observing a reduction in SDK errors. We are continuing to work on a fix.
-
monitoring Dec 15, 2025, 04:20 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 15, 2025, 04:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 09:16 PM UTC
- Resolved
- Dec 05, 2025, 03:47 AM UTC
- Duration
- 6h 30m
Timeline · 2 updates
-
investigating Dec 04, 2025, 09:16 PM UTC
We are investigation an issue with delays in experimentation results that are sliced by attributes. No data has been lost.
-
resolved Dec 05, 2025, 03:47 AM UTC
We have recovered from delays in experimentation results that are sliced by attributes. No data has been lost.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 10:52 PM UTC
- Resolved
- Dec 04, 2025, 01:05 PM UTC
- Duration
- 14h 13m
Affected: Data Export
Timeline · 4 updates
-
identified Dec 03, 2025, 10:52 PM UTC
Some customers who have configured Snowflake, BigQuery, or Redshift data export destinations may be experiencing delays in events published. There is no data loss. Exported data events are currently 32 hours behind. We are recovering steadily and will continue to send updates
-
identified Dec 04, 2025, 05:09 AM UTC
We are continuing to process the data and data is current as of 2025-12-03, 08:00:00 UTC. We'll continue to update as we process data.
-
identified Dec 04, 2025, 09:50 AM UTC
We are continuing to process the delayed data. The data is now updated through 2025-12-04, 01:00:00 UTC.
-
resolved Dec 04, 2025, 01:05 PM UTC
All of the delayed data has been processed and this incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 08:32 PM UTC
- Resolved
- Dec 03, 2025, 04:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 03, 2025, 08:32 PM UTC
Elevated error rates in apac region for server side sdks attempting to make new connections to the streaming service from 8:05 AM PT to 8:11 AM PT. The issue is now resolved
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 08:13 PM UTC
- Resolved
- Nov 26, 2025, 08:55 PM UTC
- Duration
- 42m
Affected: Flag targeting
Timeline · 3 updates
-
investigating Nov 26, 2025, 08:13 PM UTC
We are currently investigating an issue intermittently preventing our flags details pages from loading.
-
monitoring Nov 26, 2025, 08:45 PM UTC
We are no longer seeing any errors, and the issue was contained to the euw1 region. We'll continue to monitor and update this as necessary.
-
resolved Nov 26, 2025, 08:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 07:14 AM UTC
- Resolved
- Nov 24, 2025, 10:45 AM UTC
- Duration
- 3h 31m
Affected: Flag usage metrics
Timeline · 4 updates
-
identified Nov 24, 2025, 07:14 AM UTC
We have identified a delay in our event processing pipeline, and are working to mitigate the issue. Features that show flag usage metrics are affected, and data is approximately 20 minutes delayed right now.
-
identified Nov 24, 2025, 09:31 AM UTC
We are continuing to work on a fix for this issue, and remain at an approximate 20 minute delay in flag event processing.
-
monitoring Nov 24, 2025, 10:35 AM UTC
A fix has been implemented and our event processing pipeline is fully caught up. We're continuing to monitor.
-
resolved Nov 24, 2025, 10:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 09:49 PM UTC
- Resolved
- Nov 14, 2025, 12:36 AM UTC
- Duration
- 2h 46m
Affected: Config managementWeb app (app.launchdarkly.com)
Timeline · 2 updates
-
investigating Nov 13, 2025, 09:49 PM UTC
We detected elevated latencies loading the flag list and AI configs list pages. The flag list’s performance has recovered, and we continue to investigate remediation on the AI configs list page.
-
resolved Nov 14, 2025, 12:36 AM UTC
The issue with the AI Configs list page has been resolved. Impacted services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 08:38 PM UTC
- Resolved
- Nov 12, 2025, 04:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 12, 2025, 08:38 PM UTC
Between 7:37am and 8:19am PT, a small number of customers in the us-east-1 region encountered elevated error rates with Polling SDK and API requests. This was caused by a minor issue affecting a CDN POP, which has since been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 04:42 PM UTC
- Resolved
- Nov 05, 2025, 06:02 PM UTC
- Duration
- 1h 19m
Affected: Flag targeting
Timeline · 4 updates
-
investigating Nov 05, 2025, 04:42 PM UTC
We are currently investigating this issue.
-
identified Nov 05, 2025, 04:48 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 05, 2025, 04:51 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 05, 2025, 06:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 05:11 PM UTC
- Resolved
- Nov 03, 2025, 06:22 PM UTC
- Duration
- 1h 11m
Affected: Config management
Timeline · 5 updates
-
identified Nov 03, 2025, 05:11 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Nov 03, 2025, 05:11 PM UTC
We are continuing to work on a fix for this issue.
-
identified Nov 03, 2025, 05:12 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Nov 03, 2025, 06:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 03, 2025, 06:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 01, 2025, 04:05 PM UTC
- Resolved
- Nov 01, 2025, 04:05 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 01, 2025, 05:34 PM UTC
A limited number of customers (primarily in EU regions) with Polling SDK connections experienced elevated latency and errors rates between 9:05am and 9:58am PT, caused by a service incident in our CDN provider.
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2025, 05:04 PM UTC
- Resolved
- Oct 28, 2025, 05:53 PM UTC
- Duration
- 48m
Timeline · 3 updates
-
investigating Oct 28, 2025, 05:04 PM UTC
We've received reports of Live Events not loading and are investigating.
-
identified Oct 28, 2025, 05:40 PM UTC
We've identified an issue that was causing Live Events to not load (starting Oct 23 11:03am PT) and are resolving the issue.
-
resolved Oct 28, 2025, 05:53 PM UTC
We've resolved an issue causing Live Events to not load.
Read the full incident report →
- Detected by Pingoru
- Oct 28, 2025, 02:17 AM UTC
- Resolved
- Oct 28, 2025, 02:50 AM UTC
- Duration
- 33m
Affected: Experiment results analysis
Timeline · 3 updates
-
investigating Oct 28, 2025, 02:28 AM UTC
We are investigating reports of experiment results and metrics failing to load.
-
identified Oct 28, 2025, 02:38 AM UTC
We've identified an issue affecting the display of Experiment results and are working on a fix.
-
resolved Oct 28, 2025, 02:50 AM UTC
We've resolved an issue causing Experiment results to fail to load.
Read the full incident report →
