Provider
LaunchDarklyIncident detail
Server-side streaming rejected new connections across all commercial regions
Resolved incidentMajor
Timeline window
to
Outage alerts
Get alerted the next time LaunchDarkly breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update LaunchDarkly posted, oldest to newest, exactly as it appeared on their official status page.
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.
Keep exploring
More from LaunchDarkly
Neighboring incidents on LaunchDarkly's timeline and the rest of their record on OutageDeck.