# Errors on streaming SDK initialization

- Provider: [LaunchDarkly](https://down.guide/providers/launchdarkly)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-04-30 00:30 UTC
- us
- LaunchDarkly states the impact was 2026-04-29 23:45 UTC to 2026-04-30 00:05 UTC (20m)
- id: DWN-c123bf29c5
- Official page: https://stspg.io/glv1jv6rs785

## Updates from LaunchDarkly
### 2026-04-29 23:45 UTC: resolved
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.

From the builder: does your app depend on LaunchDarkly? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=launchdarkly) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention LaunchDarkly.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-c123bf29c5), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.