← Back to the carnage
LAUNCHDARKLY

🟢 LaunchDarkly fixed experiments that were returning empty results and statistical nonsense when flag variations got edited. Turns out most customers weren't paying attention anyway, so crisis mostly averted. (Auto-resolved: no updates in 24h)

⏰ May 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Issue with Experiment Results in case of Flag Variation edits

// Status page says

Apr 30 , 17:09 PDT Resolved - We have validated a fix to resolve all remaining experiments with inaccurate sample ratio mismatches (SRMs) or empty experiment results. The vast majority of experiments and experimentation customers were not impacted. Apr 29 , 17:04 PDT Monitoring - We've released a fix to prevent this issue in new experiments and iterations. We're working to

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

https://status.launchdarkly.com/incidents/nxpq0rg7y9tf

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)