Changes / LaunchDarkly / Server-side streaming rejected new connections across all commercial regions

LaunchDarkly: Major incident: Server-side streaming rejected new connections across all commercial regions

Summary

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 diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Server-side streaming rejected new connections across all commercial regions
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-19 16:58 UTC
AddedResolved time#5
Before: not present
After: 2026-03-19 16:58 UTC
AddedUpdateresolved#6
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Server-side streaming rejected new connections across all commercial regions (this change)
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.
Major incident

All LaunchDarkly changes → · LaunchDarkly profile · Markdown · JSON