LaunchDarkly incident
Server-side streaming rejected new connections across all commercial regions
Update timeline
- resolved Mar 19, 2026, 04: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.
Looking to track LaunchDarkly downtime and outages?
Pingoru polls LaunchDarkly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when LaunchDarkly reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track LaunchDarkly alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required