All Systems Operational

Uptime over the past 90 days. View historical uptime.
Flag Delivery Network (core functionality) Operational
90 days ago
99.94 % uptime
Today
Server-side streaming API Operational
90 days ago
99.93 % uptime
Today
Client-side streaming API Operational
90 days ago
99.93 % uptime
Today
Polling API Operational
90 days ago
99.93 % uptime
Today
Edge API Operational
90 days ago
100.0 % uptime
Today
Feature management (core functionality) Operational
90 days ago
99.95 % uptime
Today
Feature workflows Operational
90 days ago
99.95 % uptime
Today
Flag targeting Operational
90 days ago
99.95 % uptime
Today
Segment management Operational
90 days ago
99.95 % uptime
Today
Progressive rollouts Operational
90 days ago
99.95 % uptime
Today
Release pipelines Operational
90 days ago
99.95 % uptime
Today
Agents (core functionality) Operational
90 days ago
99.95 % uptime
Today
Config management Operational
90 days ago
99.95 % uptime
Today
Graphs Operational
90 days ago
99.94 % uptime
Today
Playgrounds and offline evaluations Operational
90 days ago
99.94 % uptime
Today
AI insights Operational
90 days ago
99.94 % uptime
Today
Experimentation (core functionality) Operational
90 days ago
99.95 % uptime
Today
Experiment management Operational
90 days ago
99.95 % uptime
Today
Experiment results processing Operational
90 days ago
99.95 % uptime
Today
Experiment results analysis Operational
90 days ago
99.95 % uptime
Today
Warehouse native experimentation Operational
90 days ago
99.95 % uptime
Today
Guarded Rollouts (core functionality) Operational
90 days ago
99.95 % uptime
Today
Rollout management Operational
90 days ago
99.95 % uptime
Today
Rollout results processing Operational
90 days ago
99.95 % uptime
Today
Rollout results analysis Operational
90 days ago
99.95 % uptime
Today
Global (core functionality) Operational
90 days ago
99.94 % uptime
Today
Authentication Operational
90 days ago
99.94 % uptime
Today
Metrics Operational
90 days ago
99.95 % uptime
Today
Web app (app.launchdarkly.com) Operational
90 days ago
99.93 % uptime
Today
Observability (core functionality) Operational
90 days ago
99.95 % uptime
Today
Frontend Operational
90 days ago
99.95 % uptime
Today
Query API Operational
90 days ago
99.95 % uptime
Today
Observability Data Ingest (Sessions, Errors) Operational
90 days ago
99.95 % uptime
Today
OpenTelemetry (Logs, Traces, Metrics) Operational
90 days ago
99.95 % uptime
Today
Feature management (non-core functionality) Operational
Context processing Operational
Data Export Operational
Flag usage metrics Operational
Experimentation (non-core functionality) Operational
Past experiment iterations Operational
Global (non-core functionality) Operational
Audit log Operational
Automations (non-core functionality) Operational
Emails and notifications Operational
Integrations and webhooks Operational
Expiring Contexts Targets Operational
Websites (non-core functionality) Operational
Docs (launchdarkly.com/docs) Operational
Website (launchdarkly.com) Operational
Account management Operational
SDKs Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Planned Upcoming API Versions Retirement Dec 31, 2026 01:00-09:00 PST

As part of our commitment to reliability and security, LaunchDarkly will retire all API versions except 20240415 on December 31, 2026.

After this date, all requests made to retired versions will stop working. To avoid disruption, customers must update integrations and workflows to use version 20240415 before the retirement date.

We previously announced the end of life (EOL) for older versions as of April 30, 2025. They have remained available during a grace period, which will end on December 31, 2026

For full details, see our API version changelog: https://launchdarkly.com/docs/api#api-version-changelog

Upgrading now ensures uninterrupted access and provides immediate improvements in performance and functionality.

We recognize this may be a large undertaking, which is why we are providing extended notice. If you need guidance, please reach out to your account team or contact our support team.
Posted on Aug 25, 2025 - 11:43 PDT

Jul 30, 2026

No incidents reported today.

Jul 29, 2026

LaunchDarkly is operational but customer action may be required
Resolved - This incident has been resolved.
Jul 29, 11:15 PDT
Update - 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 instances which did not attempt to establish a connection during this time were unaffected.

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 the Relay Proxy, please restart the Relay Proxy to re-establish connections. It should not be necessary to restart the applications behind it, but we recommend reviewing your application logs to confirm if restarting your applications is necessary.
- If you use server-side SDKs without the Relay Proxy, please restart the application to re-establish its connection to LaunchDarkly.
- Client-side and Mobile SDKs will reconnect automatically as their applications attempt to reconnect to LaunchDarkly under normal circumstances, for example when the application loads or the device regains network connectivity.
- If this does not resolve the issue for an affected application (e.g. you still see the log messages from above), please log a support ticket and we will follow up with you directly to assist with remediation.
Jul 13, 11:08 PDT
Update - We are continuing to monitor for any further issues, see our previous update for recovery steps.
Jul 10, 19:00 PDT
Update - 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 connection to LaunchDarkly.
- If re-establishing connection to the server-side SDK does not work, please create and use a second SDK key.
- If you use the Relay Proxy, please restart the Relay Proxy to re-establish connections. It should not be necessary to restart the applications behind it.
- Client-side SDKs will reconnect automatically as they restart.
- If this does not resolve the issue for an affected application (e.g. you still see the log messages from above), please log a support ticket and we will follow up with you directly to assist with remediation.
Jul 10, 16:32 PDT
Monitoring - 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.
Jul 10, 13:18 PDT
Investigating - 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.
Jul 10, 09:00 PDT

Jul 28, 2026

Delay in Session Replay and Error ingest
Resolved - The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.
Jul 28, 13:04 PDT
Monitoring - The issue with session replay and error ingest has been identified and a fix has been implemented. We expect to catch up on all backlogged data ingest in ~15 minutes. No data has been lost.
Jul 28, 12:41 PDT
Identified - Customers are experiencing delayed session replay and error ingest as of 11:03am PT. We have identified the issue and are continuing our work to resolve it. Data loss is not expected.
Jul 28, 12:24 PDT

Jul 27, 2026

No incidents reported.

Jul 26, 2026

Elevated API Latency and Errors (11:32–11:48 PT)
Resolved - Between 11:32 and 11:48 PT, customers experienced increased latency and elevated error rates on API endpoints. Latency and error rates have returned to normal, and the incident has been resolved.
Jul 26, 11:32 PDT

Jul 25, 2026

No incidents reported.

Jul 24, 2026

No incidents reported.

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage