Warehouse Data Exports delayed
Warehouse Data Exports were delayed for LaunchDarkly's Data Export component. LaunchDarkly reported the incident resolved and the exports work normally again. The outage lasted about 5 hours and 50 minutes.
State
Resolved
Started
Lasted
5 h 50 min
Worst impact
Degraded
Timeline
3 updatesIdentified
4 h 26 min 76%
Monitoring
1 h 24 min 24%
Updates
Times in UTCAs posted by LaunchDarkly
Warehouse Data Exports are working normally again.
We've identified an issue with one of our upstream providers. We've escalated it to them and in the meanwhile have a deployed a workaround on our end as well. Data Exports are successful now and we're working on the backfill. Current delay stands at ~2 hours.
We've identified an issue with our Warehouse Data Export pipeline. A fix is being implemented. Warehouse Data Exports are operating on a delay of ~4 hours right now.
Affected components
2LaunchDarkly in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
8
Median duration
51 min
This incident
6.9× the median
Other LaunchDarkly incidents
All incidents
LaunchDarkly·Email notifications are not being delivered
LaunchDarkly email notifications were not delivered, including verification emails for sign-ins from a new device or browser. The components affected were Emails and notifications, and Automations (non-core functionality) for Emails and notifications. LaunchDarkly reports that the incident is resolved, and it lasted 26 minutes.

LaunchDarkly·delayed event processing
A scaling inflection point in our realtime event warehouse led to a delay for some event ingestion. The engineering team has remediated the problem and all events should be caught up. Some customers may have seen delays in experiments and in guarded release processing. This is now resolved and the team will carefully monitor.

LaunchDarkly·Elevated 5xx Errors (15:11–15:32 UTC)
Between 15:11 and 15:32 UTC today, we observed elevated 5xx errors affecting requests across our services. Approximately 0.7% of requests failed during this period (99.3% succeeded). This incident has been resolved.

LaunchDarkly·Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
This incident has been resolved.

LaunchDarkly·Elevated error rates in the LaunchDarkly application
This incident has been resolved.
Follow LaunchDarkly
Your coding agent knows when LaunchDarkly is down, and tells you when a failure is theirs, not yours. You can also get LaunchDarkly incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "launchdarkly" and tell me if LaunchDarkly has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=launchdarkly/feed subscribe https://outages.live/feed.xml?providers=launchdarklyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane