CompaniesLaunchDarklyIncidents
LaunchDarkly: Issues with Observability Alert Notification
Affected components: Automations (non-core functionality) - Emails and notificationsEmails and notifications
Timeline of updates
- investigating
We are currently investigating an issue prevent Observability alert notifications from being delivered.
- identified
We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational.
- monitoring
A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.
- resolved
Observability alerts are functioning and delayed alerts have been redelivered.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d3588e157ab6d81a…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by LaunchDarkly, started 2026-04-28 18:34 UTC, resolved after 51 min, 4 update(s).
- Title
- Issues with Observability Alert Notification
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/8kwh4h4ljqzd
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on April 28, 2026LaunchDarkly in April 2026MarkdownJSON