← Back to the carnage
LAUNCHDARKLY
🟡 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)
// The official story
Server sdks are down
// Status page says
Jul 10 , 12:21 PDT Investigating - We are investigating continued impact to customers' server SDK caused by the previous incident (https://status.launchdarkly.com/incidents/chywwz01ptb0). If customers are receiving SDK or Relay Proxy 401s please re-establish connections.
🔗 Official status page (for the PR-approved version)
https://status.launchdarkly.com/incidents/44vx9yyr4vgwLaunchdarkly'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
🔴 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)
🟢 LAUNCHDARKLY
Jul 10, 2026
🟡 LaunchDarkly's dashboard decided to play hide-and-seek with its users. The irony of a feature flag company unable to show you your own flags isn't lost on anyone. Engineers are investigating why their control panel learned to become completely uncontrollable. (Auto-resolved: no updates in 24h)