LaunchDarkly Status · History · Incident #4629
RESOLVEDObservability OpenTelemetry Ingest Delay
Minor · Started Jun 15, 2026 · 10:02 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
LaunchDarkly Status · History · Incident #4629
RESOLVEDMinor · Started Jun 15, 2026 · 10:02 AM
Duration
36m
Severity
Minor
Detection lead
—
User reports
—
Summary
The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.
Started
Jun 15, 2026 · 10:02 AM
Resolved
Jun 15, 2026 · 10:38 AM
Duration
36m
Severity
Minor
Event timeline
Identified
Jun 15 · 10:26 AM LaunchDarklySome customers are experiencing delayed Observability data ingest for OpenTelemetry data. We have identified the issue and are continuing our work to resolve it. Observability signals (errors / logs / traces / OTel metrics) are currently delayed by ~6 minutes on average. Data ingest delays began at 10:02am and are improving as of 10:16am PT.
Monitoring
Jun 15 · 10:33 AM LaunchDarklyThe issue with Observability data ingest for OpenTelemetry data has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved. Observability signals (errors / logs / traces / OTel metrics) are currently delayed by <1 minutes on average.
Resolved
Jun 15 · 10:38 AM LaunchDarklyThe issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026