Companies / LaunchDarkly / incidents
LaunchDarkly: Server-side streaming rejected new connections across all commercial regions
LaunchDarkly reported a major incident affecting new server-side SDK streaming connections across all commercial regions, causing 500/503 errors. Start and resolution were both recorded as 2026-03-19 16:58 UTC, with a computed duration of 0 min. The vendor reported deploying mitigation.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- resolved
Server-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.
Rewindex changes for this incident
- Major incident: Server-side streaming rejected new connections across all commercial regions 2026-03-19 16:58 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). LaunchDarkly profile · Recent LaunchDarkly incidents · Markdown · JSON