← Back to LaunchDarkly History
major✓ Resolved
Server-side streaming rejected new connections across all commercial regions
Status
resolved
Duration
0m
Updates
1
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
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.
📊 TECHNICAL DETAILS
Internal ID
ece4bc8e-27bf-4106-9ba8-cd74ad6469da
External ID
dfqd9pff4533
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
0m
Total Duration
1
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed