LaunchDarkly logo
ALL SYSTEMS OPERATIONAL

LaunchDarkly systems
are operational.

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

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

  • ALL SYSTEMS OPERATIONAL

    LaunchDarkly is up and running.

    Last incident resolved 1 week ago


    No active incidents at this time. Noticed something?
  • 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

    23

    Since Sep 2025

  • Major / Critical

    4

    4 high-impact incidents

  • Minor Incidents

    19

    Avg. 0.2 per day

  • Median Resolution

    51m

    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
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 →
Elevated errors affecting LaunchDarkly application requests
Jun 11, 2026 · 9:23 PM 35m
Major
Resolved
Details →
Delays in event ingestion
Jun 8, 2026 · 1:46 PM 4d 17h 6m
Minor
Resolved
Details →
Flag dashboard is failing to load
Jun 3, 2026 · 12:31 PM 55m
Major
Resolved
Details →
Issue with Slack notifications for Segment approvals
May 22, 2026 · 11:40 AM 1h 1m
None
Resolved
Details →
Event Ingestion Delays
May 19, 2026 · 7:49 AM 5m
Major
Resolved
Details →
Delayed processing of Session Replay and Error data
May 15, 2026 · 5:03 PM 1h 9m
Minor
Resolved
Details →
Elevated Streaming Errors in APAC region
May 5, 2026 · 8:58 PM 27m
Minor
Resolved
Details →
Experiment and multi-armed bandit results delayed
May 4, 2026 · 12:47 PM 37m
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 23 incidents, of which 4 were major or critical. The median resolution time is 51m.

  • 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.