Elevated Streaming Errors in Europe
May 4, 10:14 UTCMay 4, 16:23 UTC
Duration
6h 8m
Impact
Minor
Root cause
Not disclosed
LaunchDarkly, 90 days
16 incidents
Affected
Server-side streaming APIFlag Delivery Network (core functionality) - Server-side streaming API
Final update
This incident has been resolved.
Timeline
- Resolved · May 4, 16:23 UTC
This incident has been resolved.
- Monitoring · May 4, 15:47 UTC
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.
- Identified · May 4, 14:30 UTC
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.
- Identified · May 4, 12:51 UTC
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
- Investigating · May 4, 10:14 UTC
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.
More from LaunchDarkly
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Aug 2620:00 UTC | Flag delivery errors in Streaming API | minor | 0m |
| Aug 2412:20 UTC | Email delivery failure affecting sign-up verification and notification emails | minor | 1h 15m |
| Aug 1710:36 UTC | Flag Updates via Polling API delayed | minor | 5h 26m |
| Aug 1414:47 UTC | Flag Updates delayed in US Region | minor | 2h |
| Aug 719:29 UTC | Elevated errors on server-side SDK streaming connections | minor | 46m |
| Jul 3117:44 UTC | Investigating - Known Impact | minor | 5h 10m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.