Major incident
LaunchDarkly: Server-side streaming rejected new connections across all commercial regions
Mar 19, 2026, 16:58 UTC
started
16:58 UTC
resolved
<1 min
duration
Current status of LaunchDarkly: Operational — live LaunchDarkly status
Timeline
- Mar 19, 2026, 16:58 UTCresolvedServer-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 PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.
Updates as published by LaunchDarkly (original).
Other services with incidents at the same time
- Apache Software Foundation 17:48 UTC · Wiki - Confluence (cwiki.apache.org) is experiencing issues.
- Survicate 17:42 UTC · Issues with logging in and accessing workspaces
- SimplePractice 17:22 UTC · Limited Feature Interruption
- Cloudinary 16:48 UTC · Errors with Account Creation
More LaunchDarkly incidents
- October 15, 2026 Elevated 5xx Errors (15:11–15:32 UTC)
- October 3, 2026 Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
- October 2, 2026 Elevated error rates in the LaunchDarkly application
- July 10, 2026 Web application unavailable and flag delivery evaluations have elevated failure rate
- July 6, 2026 High volume of error alerts related to flag delivery network.
- June 12, 2026 Elevated errors affecting LaunchDarkly application requests