← Back to LaunchDarkly History
minor✓ Resolved

Elevated Streaming Errors in Europe

LaunchDarklyMon, May 4, 2026, 12:28 PM
Status
resolved
Duration
3h 56m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedMon, May 4, 2026, 04:25 PM
This incident has been resolved.
monitoringMon, May 4, 2026, 03:47 PM
We've implemented a fix and have mitigated impact as of 8:35am PT. Streaming SDKs should be able to connect successfully at this time.
identifiedMon, May 4, 2026, 02:30 PM
We're continuing to address the root cause of the elevated error rate. Server SDKs may require additional time to initialize while requests are retried.
identifiedMon, May 4, 2026, 12:51 PM
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
investigatingMon, May 4, 2026, 12:28 PM
We are investigating elevated error rates for streaming initialization in the Europe region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.

📊 TECHNICAL DETAILS

Internal ID
34ea3ce1-225e-4f76-a368-4842040c95ba
External ID
956d9bdtw9jt
🕐 Started
Mon, May 4, 2026, 12:28 PM
🔄 Last Updated
Mon, May 4, 2026, 04:25 PM
✓ Resolved
Mon, May 4, 2026, 04:25 PM
MINOR
Impact Level
3h 56m
Total Duration
4
Status Updates
Affected Components
Server-side streaming API
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed