LAUNCHDARKLY

⚪ LaunchDarkly admitted some of your event data ghosted you during two separate windows—turns out 'event ingestion' doesn't mean the data actually stays. They're backfilling now, but your feature flags may be running on incomplete intel. At least they're honest about losing things instead of pretending it never happened. (Auto-resolved: no updates in 24h)

⏰ Jun 13, 2026 Fixed (for now) spotted via status_rss

// The official story

Delays in event ingestion

// Status page says

Jun 13 , 06:52 PDT Resolved - This incident has been resolved. Jun 12 , 15:15 PDT Update - We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are

🔗 Official status page (for the PR-approved version)

https://status.launchdarkly.com/incidents/52yhcr551t6w

Launchdarkly's Greatest Hits

🟢 LAUNCHDARKLY Jul 10, 2026

🟡 Mobile and server SDKs decided intermittent existence is their brand now. Apparently last incident's therapy didn't take. If you're getting 401s, try turning your SDK off and on again—like it's a toaster. (Auto-resolved: no updates in 24h)

🟢 LAUNCHDARKLY Jul 10, 2026

🟡 LaunchDarkly's server SDKs are throwing 401s like confetti after yesterday's disaster. The fix? Turn it off and on again, apparently. Nothing says 'we have it under control' like telling customers to manually reconnect their infrastructure. (Auto-resolved: no updates in 24h)

🟢 LAUNCHDARKLY Jul 10, 2026

🔴 Feature flags forgot how to flag. Web app ghosted users while flag delivery network decided to ghost back—elevated failure rates all around. Engineers found the root cause faster than anyone expected (miracle, truly). (Auto-resolved: no updates in 24h)

🟢 LAUNCHDARKLY Jul 10, 2026

🟠 Your feature flags stopped flagging, and the UI went full ghost mode. The engineers identified the problem in 10 minutes—which in incident time means they found the typo 4 dashboards ago. Fix allegedly deployed, but we're all waiting for the "just kidding" follow-up post. (Auto-resolved: no updates in 24h)