← Back to the carnage
LAUNCHDARKLY
🟡 LaunchDarkly's documentation site went dark, proving that even the feature flag experts can't control their own infrastructure. Engineers are currently having an existential crisis in the incident channel. Ironic considering their entire business is about controlling what goes live. (Auto-resolved: no updates in 24h)
// The official story
Docs site is down
// Status page says
Apr 20 , 15:04 PDT Investigating - We are currently investigating this issue.
🔗 Official status page (for the PR-approved version)
https://status.launchdarkly.com/incidents/p33q94lrcrslLaunchdarkly'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)