LaunchDarkly incident: Issues with Observability Alert Notification

Affected components

• Emails and notifications

1. resolvedApr 28, 2026, 19:25 UTC

   Observability alerts are functioning and delayed alerts have been redelivered.

2. monitoringApr 28, 2026, 19:10 UTC

   A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.

3. identifiedApr 28, 2026, 18:38 UTC

   We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational.

4. investigatingApr 28, 2026, 18:34 UTC

   We are currently investigating an issue prevent Observability alert notifications from being delivered.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Missing Metrics in Cloud Console — US East (us-east-1)Major · Apr 28, 2026, 14:46 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• DigitalOcean: Elevated 5xx “context canceled” errors impacting serverless inferenceMinor · Apr 28, 2026, 13:45 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• ReadMe: Creating branches is resulting in 500 errorsMinor · Apr 28, 2026, 18:38 UTC
• Inngest: Increased function execution latencyMinor · Apr 28, 2026, 19:11 UTC
• Discord: Connection DelaysMinor · Apr 28, 2026, 19:20 UTC

How often does LaunchDarkly have incidents?

LaunchDarkly reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 19m. See LaunchDarkly's uptime and incident history