LaunchDarkly logo
ACTIVE INCIDENT DETECTED

LaunchDarkly is
experiencing issues.

Pulsetic detects outages before the provider officially reports them. Monitoring since Sep 2025 · 66 incidents caught

Last checked: 3 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • MINOR · MONITORING

    LaunchDarkly is operational but customer action may be required

    Started 1 week ago · Jul 10, 2026 · 9:00 AM UTC

    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.


    View official incident → Having issues too?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    27

    Since Sep 2025

  • Major / Critical

    5

    5 high-impact incidents

  • Minor Incidents

    22

    Avg. 0.2 per day

  • Median Resolution

    58m

    P95: 27h 50m

LaunchDarkly Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Web application unavailable and flag delivery evaluations have elevated failure rate
Jul 10, 2026 · 10:10 AM 1h 9m
Critical
Resolved
Details →
Launchdarkly UI is down and flag evaluation errors are occuring
Jul 10, 2026 · 9:16 AM 1h 31m
None
Resolved
Details →
LaunchDarkly is operational but customer action may be required
Jul 10, 2026 · 9:00 AM Ongoing
Minor
Monitoring
Details →
Frequentist experiments cannot be saved or started
Jul 8, 2026 · 11:03 AM 1h 38m
Minor
Resolved
Details →
Delays in Experimentation and Guarded Rollout results
Jul 7, 2026 · 8:10 AM < 1m
None
Resolved
Details →
High volume of error alerts related to flag delivery network.
Jul 6, 2026 · 1:30 PM 51m
Major
Resolved
Details →
Verification emails not being sent
Jul 6, 2026 · 7:33 AM 1h 19m
Minor
Resolved
Details →
Elevated error rates on event data ingestion endpoints
Jul 3, 2026 · 7:29 AM 1h 37m
Minor
Resolved
Details →
LaunchDarkly.com and LaunchDarkly.com/docs unavailable for some
Jun 17, 2026 · 12:43 PM 5h 46m
Minor
Resolved
Details →
Observability OpenTelemetry Ingest Delay
Jun 15, 2026 · 10:02 AM 36m
Minor
Resolved
Details →

Get alerted the moment LaunchDarkly goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is LaunchDarkly down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does LaunchDarkly go down?

    Based on our 90-day data, we've detected 27 incidents, of which 5 were major or critical. The median resolution time is 58m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.