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

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-03-19 16:58 UTC · Resolved: 2026-03-19 16:58 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://stspg.io/9v1n684p4wtp](https://stspg.io/9v1n684p4wtp)
- [Company: LaunchDarkly](https://rewindex.com/company/launchdarkly.md)

## 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, sol)_
## Timeline of updates

- **resolved** 2026-03-19 16:58 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.

## Rewindex changes for this incident

- 2026-03-19 16:58 UTC: [Major incident: Server-side streaming rejected new connections across all commercial regions](https://rewindex.com/change/i818e8e2d96a6d7.md)


---
Canonical: https://rewindex.com/company/launchdarkly/incidents/dfqd9pff4533 · Markdown: https://rewindex.com/company/launchdarkly/incidents/dfqd9pff4533.md · JSON: https://rewindex.com/api/v1/companies/launchdarkly/incidents/dfqd9pff4533 · Generated 2026-10-18T09:35:07.850Z