Home
/
Status
/
Service
Feature flags and experimentation for software releases.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 1h ago
51
Components
0
Active incidents
1
Maintenance
8.7%
90d uptime
LaunchDarkly.com and LaunchDarkly.com/docs unavailable for some
Jun 17, 7:43 PM
Normalized official status-page data for incidents, maintenance, components, and history.
8.7%
Known uptime
23 known history days
51
Components tracked
0 outage, 0 degraded
52
Incidents indexed
0 active right now
50
Maintenance windows
1 active or scheduled
Components with the most recent status-page events.
Docs (launchdarkly.com/docs)
Operational
Observability (core functionality)
Operational
OpenTelemetry (Logs, Traces, Metrics)
Operational
Website (launchdarkly.com)
Operational
Websites (non-core functionality)
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
2
operational days
0
degraded days
20
outage days
1
maintenance days
67
unknown days
Latest outages and degradations detected from the official status page.
We're now seeing restored access in the affected regions.
The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.
Monitoring has confirmed no further impact outside of the initially reported 7:30-7:37pm PT timeframe
This incident has been resolved.
The incident has been resolved and the flag dashboard is successfully loading.
We have confirmed Slack notifications are now coming through for segment approvals again.
This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused. Results were delayed from 6:58am PDT to 7:52am PDT
All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.
We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.
All experiment and multi-armed bandit result data is caught up. No data was lost.
Scheduled and completed maintenance windows are separated from incidents.
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.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Launchdarkly status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.launchdarkly.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 51 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Flag Delivery Network (core functionality) Mechanism by which flags are delivered to LaunchDarkly SDKs | Operational | Group | Not recorded |
Feature management (core functionality) Ability to manage flags in LaunchDarkly’s UI (app.launchdarkly.com) and API | Operational | Group | Not recorded |
Agents (core functionality) Ability to manage agentic workflows in LaunchDarkly’s UI and API | Operational | Group | Not recorded |
Experimentation (core functionality) Ability to process and manage experiment data through LaunchDarkly’s UI and API | Operational | Group | Not recorded |
Guarded Rollouts (core functionality) Safely release features with real-time monitoring and rollback capabilities | Operational | Group | Not recorded |
Global (core functionality) | Operational | Group | Not recorded |
Observability (core functionality) | Operational | Group | 6/15/2026 |
Feature management (non-core functionality) Secondary functionality in LaunchDarkly’s UI (app.launchdarkly.com) and API | Operational | Group | Not recorded |
Experimentation (non-core functionality) Secondary functionality for viewing and managing experiment data in LaunchDarkly’s UI and API | Operational | Group | Not recorded |
Global (non-core functionality) | Operational | Group | Not recorded |
Automations (non-core functionality) | Operational | Group | Not recorded |
Websites (non-core functionality) | Operational | Group | 6/18/2026 |
Audit log Recording and publication of audit log events | Operational | Component | Not recorded |
Authentication UI & API Authentication Mechanisms | Operational | Component | Not recorded |
Config management UI and APIs used to manage configs | Operational | Component | Not recorded |
Context processing Ingestion and recording of contexts | Operational | Component | Not recorded |
Emails and notifications Outbound emails and notifications sent by LaunchDarkly | Operational | Component | Not recorded |
Experiment management Creating, editing, starting, and stopping experiments | Operational | Component | Not recorded |
Feature workflows Workflow functionality for automated features like scheduled changes and approvals | Operational | Component | Not recorded |
Frontend | Operational | Component | Not recorded |
Past experiment iterations Viewing past iterations | Operational | Component | Not recorded |
Rollout management Coordinate and oversee feature rollouts across multiple environments | Operational | Component | Not recorded |
Server-side streaming API Real-time flag updates for server-side SDKs | Operational | Component | Not recorded |
Client-side streaming API Real-time flag updates for client-side SDKs | Operational | Component | Not recorded |
Data Export Recording and publication of events to Data Export destinations | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Launchdarkly is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
