Server-side streaming rejected new connections across all commercial regions

What to do

• Check whether you use LaunchDarkly in ap-southeast-1, eu, eu-west-1, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-03-19 16:58 UTC and 2026-03-19 16:58 UTC may need a replay.

• Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 1

1. resolvedMar 19, 2026, 4:58 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.