
LaunchDarkly Status
Real-time updates of LaunchDarkly issues and outages
LaunchDarkly status is Operational
Observability Data Ingest (Sessions, Errors)
You're checking on LaunchDarkly - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
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 identified the root cause as elevated database utilization and are actively working to resolve the backlog. We will provide updates as processing returns to normal.
LaunchDarkly Outage Survival Guide
LaunchDarkly Components
LaunchDarkly Flag Delivery Network (core functionality)
Server-side streaming API
Client-side streaming API
Polling API
Edge API
LaunchDarkly Feature management (core functionality)
Feature workflows
Flag targeting
Segment management
Progressive rollouts
Release pipelines
LaunchDarkly Experimentation (core functionality)
Experiment management
Experiment results processing
Experiment results analysis
Warehouse native experimentation
LaunchDarkly Guarded Rollouts (core functionality)
Rollout management
Rollout results processing
Rollout results analysis
LaunchDarkly Global (core functionality)
Authentication
Metrics
Web app (app.launchdarkly.com)
LaunchDarkly Observability (core functionality)
Frontend
Query API
Observability Data Ingest (Sessions, Errors)
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 identified the root cause as elevated database utilization and are actively working to resolve the backlog. We will provide updates as processing returns to normal.