Live

Warehouse Data Exports delayed

0

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 updates
07:1308:4010:0811:3613:03
DegradedUpdate postedTimes in UTC

Identified

4 h 26 min 76%

Monitoring

1 h 24 min 24%

Updates

Times in UTC

As posted by LaunchDarkly

Resolved

Warehouse Data Exports are working normally again.

Monitoring

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.

Identified

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

2
Data ExportFeature management (non-core functionality) - Data Export

LaunchDarkly in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

8

Days with an incident

8

Median duration

51 min

This incident

6.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h 55 min
median 51 min
90 days agoToday

Other LaunchDarkly incidents

All incidents

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.

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

RSS
https://outages.live/feed.xml?providers=launchdarkly
Slack
/feed subscribe https://outages.live/feed.xml?providers=launchdarkly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane