Incidentsby GlyphErrors on streaming SDK initialization
Apr 29, 23:45 UTCApr 29, 23:45 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
LaunchDarkly, 90 days
9 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 historyEmail notifications are not being deliveredlasted 26mdelayed event processinglasted 0mElevated 5xx Errors (15:11–15:32 UTC)lasted 0mDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentationlasted 1h 37mElevated error rates in the LaunchDarkly applicationlasted 18h 55mFlag delivery errors in Streaming APIlasted 15m