What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with LaunchDarkly now? Check the current statusAffected services
Updates (6)
- Jul 29, 2026, 06:15 PMLaunchDarkly is operational but customer action may be required
This incident has been resolved.
LaunchDarkly ↗ - Jul 13, 2026, 06:08 PMLaunchDarkly is operational but customer action may be required
All LaunchDarkly services are operational, though some customers need to take action to restore their connections to our Flag Delivery Network. Customers continue to successfully reestablish connections by completing the action guidance below and we continue to support customers working through the residual impact. SDKs and Relay Proxy instances which attempted to establish a connection to LaunchDarkly on July 10 between 09:11 and 11:42 AM PT were intermittently affected. This includes situations where the host application was restarted or redeployed during this time. SDKs and Relay Proxy ins
LaunchDarkly ↗ - Jul 11, 2026, 02:00 AMLaunchDarkly is operational but customer action may be required
We are continuing to monitor for any further issues, see our previous update for recovery steps.
LaunchDarkly ↗ - Jul 10, 2026, 11:32 PMLaunchDarkly is operational but customer action may be required
Customers continue to successfully reestablish connections to our streaming services. We recommend reviewing your application logs for the incident window. Affected SDKs emit messages—varying by language—that contain any of the following: "giving up permanently," "Invalid SDK key," "unauthorized," "not authorized," or "401." Any service that logged these messages may be unable to receive flag updates or send event data until it is restarted. Here are the recommended actions for each affected application: - If you use server-side SDKs, please restart the application to re-establish its conne
LaunchDarkly ↗ - Jul 10, 2026, 08:18 PMLaunchDarkly is operational but customer action may be required
Our Flag Delivery services have recovered and we're observing an increase in customer traffic successfully reestablish connections to our streaming services. Customers who continue to encounter 401 connection errors in their SDKs or Relay Proxy instances are advised to restart their applications and/or Relay Proxy instances.
LaunchDarkly ↗ - Jul 10, 2026, 07:21 PMLaunchDarkly is operational but customer action may be required
We are investigating continued impact to customers' mobile and 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.
LaunchDarkly ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow LaunchDarkly's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.