Guardian

← All providers · Developer Tools

LaunchDarkly.

1 service independently monitored by Guardian

Atom feed of incidents & status changes

GUARDIAN-MEASURED

◐ AUTH REQUIREDAll systems responding (auth-walled endpoints)

Our keyless probes, every 5 minutes. Independent of the vendor.

VENDOR-REPORTED

■ ALL SYSTEMS OPERATIONAL

Their status feed, fetched 2m ago. Shown for reference.

Two lanes. Never merged into one number.

01⁄GUARDIAN-MEASURED · 90-DAY WINDOW · 30-DAY NARROW WINDOW

Measured by Guardian probes only. Mobile rows show a separately computed trailing 30-day percentage beside the 30 visible cells.

APIs

  • API v2◐ AUTH REQUIRED
    90 days ago100 % reachable · grade A · since 2026-06-15 · auth blocks deep probes; reachability only, not correctness · no changes in 50d100 % reachable · grade A · 30 d · auth blocks deep probes; reachability only, not correctness · no changes in 50d · 30 dtoday

MCP servers

□ NO DATA · no MCP servers monitored

02⁄VENDOR-REPORTED · TRACKED SINCE 2026-06-12 · 52-DAY WINDOW

Vendor-reported components

As self-reported by LaunchDarkly’s official status feed, grouped to mirror its status page. Shown for reference. The Guardian-measured statuses and uptime below are probed independently and unaffected by this data.

Agents (core functionality)Operational4 of 4 operational
  • AI insightsOperational
  • Config managementOperational
  • GraphsOperational
  • Playgrounds and offline evaluationsOperational
Automations (non-core functionality)Operational3 of 3 operational
  • Emails and notificationsOperational
  • Expiring Contexts TargetsOperational
  • Integrations and webhooksOperational
Experimentation (core functionality)Operational4 of 4 operational
  • Experiment managementOperational
  • Experiment results analysisOperational
  • Experiment results processingOperational
  • Warehouse native experimentationOperational
Experimentation (non-core functionality)Operational1 of 1 operational
  • Past experiment iterationsOperational
Feature management (core functionality)Operational5 of 5 operational
  • Feature workflowsOperational
  • Flag targetingOperational
  • Progressive rolloutsOperational
  • Release pipelinesOperational
  • Segment managementOperational
Feature management (non-core functionality)Operational3 of 3 operational
  • Context processingOperational
  • Data ExportOperational
  • Flag usage metricsOperational
Flag Delivery Network (core functionality)Operational4 of 4 operational
  • Client-side streaming APIOperational
  • Edge APIOperational
  • Polling APIOperational
  • Server-side streaming APIOperational
Global (core functionality)Operational3 of 3 operational
  • AuthenticationOperational
  • MetricsOperational
  • Web app (app.launchdarkly.com)Operational
Global (non-core functionality)Operational1 of 1 operational
  • Audit logOperational
Guarded Rollouts (core functionality)Operational3 of 3 operational
  • Rollout managementOperational
  • Rollout results analysisOperational
  • Rollout results processingOperational
Observability (core functionality)Operational4 of 4 operational
  • FrontendOperational
  • Observability Data Ingest (Sessions, Errors)Operational
  • OpenTelemetry (Logs, Traces, Metrics)Operational
  • Query APIOperational
Websites (non-core functionality)Operational2 of 2 operational
  • Docs (launchdarkly.com/docs)Operational
  • Website (launchdarkly.com)Operational
Other componentsOperational2 of 2 operational
  • Account managementOperational
  • SDKsOperational

Vendor-reported data via status.launchdarkly.com (fetched 2m ago)

OperationalDegraded PerformancePartial OutageMajor OutageMaintenanceNo dataGrade: A ≥99.9% · B ≥99% · C ≥95% · D ≥90% · F <90%

03⁄PAST INCIDENTS

Past incidents

No incidents reported.

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedOpenTelemetry (Logs, Traces, Metrics): Degraded performance · resolved after 5h 10m

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedObservability Data Ingest (Sessions, Errors): Degraded performance · resolved after 40m

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedSDKs: Major outage · resolved after 1h
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedAccount management: Partial outage · resolved after 30m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedFrontend: Partial outage · resolved after 50m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedWeb app (app.launchdarkly.com): Partial outage · resolved after 1h 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedWarehouse native experimentation: Partial outage · resolved after 1h 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedSegment management: Partial outage · resolved after 1h 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedRollout results processing: Partial outage · resolved after 1h 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedRollout results analysis: Partial outage · resolved after 1h 5m

+25 more events this day not shown

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedExperiment management: Degraded performance · resolved after 1h 36m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedServer-side streaming API: Partial outage · resolved after 15m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedFlag targeting: Major outage · resolved after 3h
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedFeature workflows: Major outage · resolved after 3h
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedEmails and notifications: Degraded performance · resolved after 5m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedEmails and notifications: Degraded performance · resolved after 10m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedRollout results analysis: Degraded performance · resolved after 45m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedMetrics: Degraded performance · resolved after 45m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedFlag usage metrics: Degraded performance · resolved after 45m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedExperiment results processing: Degraded performance · resolved after 45m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedAI insights: Degraded performance · resolved after 45m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedWebsite (launchdarkly.com): Degraded performance · resolved after 5h 43m
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedDocs (launchdarkly.com/docs): Degraded performance · resolved after 5h 43m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedOpenTelemetry (Logs, Traces, Metrics): Degraded performance · resolved after 6m

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedWarehouse native experimentation: Degraded performance · resolved (start not recorded)
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedData Export: Degraded performance · resolved (start not recorded)

  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedExperiment results processing: Degraded performance · resolved (start not recorded)
  • VENDOR-REPORTEDVendor-reported✓ RESOLVEDResolvedExperiment results analysis: Degraded performance · resolved (start not recorded)

Vendor-reported incidents are shown from , when Guardian began recording this status feed’s transitions. Earlier vendor incidents are not shown.