LaunchDarkly
Developer Tools
Components
90-Day Uptime History
Event Log
11h ago
11h ago
11h ago
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.
11h ago
Feb 13, 3:40 AM
Feb 13, 3:40 AM
Feb 13, 1:32 AM
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.
Feb 13, 1:31 AM
Feb 12, 3:54 AM
Feb 12, 3:54 AM
Feb 12, 3:51 AM
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.
Feb 12, 3:50 AM
Feb 10, 9:02 AM
Feb 10, 9:02 AM
Feb 10, 8:42 AM
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.
Feb 10, 8:42 AM
Feb 9, 9:49 PM
Feb 9, 9:48 PM
Feb 9, 9:47 PM
Feb 9, 9:46 PM
Feb 9, 9:45 PM
Feb 9, 9:44 PM
Feb 9, 9:43 PM
Feb 9, 9:42 PM
Feb 9, 9:41 PM
Feb 9, 9:40 PM
Feb 9, 9:39 PM
Feb 9, 9:38 PM
Sites Using LaunchDarkly
12 analyzed sites depend on LaunchDarkly. If this service goes down, these sites may be affected.
Detection patterns, related technologies, and usage stats
Live dashboard for all monitored developer services
See how LaunchDarkly status affects a real site
Status data polled every 60 seconds. History retained for 90 days. Snapshots stored on status changes.