When did the incident start and end?

It started at 2026-11-09 14:48 UTC and ended at 2026-11-09 15:14 UTC. It lasted 26 min.

How do I get alerts for LaunchDarkly?

Subscribe to the LaunchDarkly live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of LaunchDarkly. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

LaunchDarklyIncident ·

Email notifications are not being delivered

Q: What happened?

LaunchDarkly reported "Email notifications are not being delivered" on its status page at 2026-11-09 14:48 UTC. 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.

Q: What is affected?

LaunchDarkly lists these components: Emails and notifications, Automations (non-core functionality) - Emails and notifications.

ResolvedOfficial update

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.

State

Resolved

Started

Lasted

26 min

Worst impact

Degraded

Timeline

3 updates

14:4814:5415:0115:0715:14

DegradedUpdate postedTimes in UTC

Investigating

21 min 81%

Monitoring

5 min 19%

Updates

Times in UTC

As posted by LaunchDarkly

Resolved

Delivery is fully restored. This incident has been resolved.

Monitoring

We identified an issue that prevented some email notifications from LaunchDarkly from being delivered, including verification emails sent when signing in from a new device or browser. A fix has been applied and emails are now being delivered. We're continuing to monitor to confirm delivery is fully restored.

Investigating

We are investigating an issue where email notifications from LaunchDarkly are not being delivered. This includes emails such as organization verification codes sent when signing in from a new device or browser. We are working to restore email delivery and will post an update as soon as it is resolved.

Affected components

Emails and notificationsAutomations (non-core functionality) - Emails and notifications

LaunchDarkly in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 15 min

This incident

65% shorter than the median

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

18 h 55 min

median 1 h 15 min

90 days agoToday

Other LaunchDarkly incidents

All incidents

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.

Resolved

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.

Resolved

LaunchDarkly·Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation

This incident has been resolved.

Resolved

LaunchDarkly·Elevated error rates in the LaunchDarkly application

This incident has been resolved.

Resolved

LaunchDarkly·Flag delivery errors in Streaming API

This incident has been resolved. Between 12:00 and 12:12 PM PDT on August 26, server-side SDKs establishing new streaming connections experienced elevated error rates. Existing streaming connections were not affected, and polling requests continued to be served with error rates below 1%. Some requests to the LaunchDarkly web application also experienced elevated errors between approximately 11:29 AM and 12:03 PM PDT. The issue was caused by an internal configuration change, which has been reverted. All systems have recovered and are operating normally. No customer data was lost or compromised.

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.

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