Errors on streaming SDK initialization
Apr 30, 00:30 UTCApr 29, 23:45 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
LaunchDarkly, 90 days
16 incidents
Affected
Not listed by the vendor.
Final update
We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.
Timeline
- Resolved · Apr 29, 23:45 UTC
We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.
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.