← Back to LaunchDarkly History
minor✓ Resolved
Investigating - Known Impact
Status
resolved
Duration
5h 11m
Updates
3
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedFri, Jul 31, 2026, 10:55 PM
This incident has been resolved.
monitoringFri, Jul 31, 2026, 09:58 PM
The issue with Observability Traces has been identified and a fix has been implemented. We have recovered most trace data that was missing from July 30th 5:16pm to July 31st 10:59am PT. We will resolve the incident once we fully complete data recovery (expected to complete by 5pm PT).
identifiedFri, Jul 31, 2026, 05:59 PM
Customers are experiencing missing Observability Traces ingested from July 30th 5:16pm until July 31st 10:59am PT. Observability Logs / Metrics are unaffected.
We have identified the issue and are continuing our work to recover the missing Traces data.
investigatingFri, Jul 31, 2026, 05:44 PM
All customers are experiencing missing Observability Traces starting July 30th at 5:16pm PT. We are investigating and will provide updates as they become available. Trace data is not lost and we are working to recover it.
📊 TECHNICAL DETAILS
Internal ID
9a2b8cd1-15de-4f1e-9a91-dfe6e0dad33c
External ID
pgwlk8x3h6vx
🕐 Started
Fri, Jul 31, 2026, 05:44 PM
🔄 Last Updated
Fri, Jul 31, 2026, 10:55 PM
✓ Resolved
Fri, Jul 31, 2026, 10:55 PM
MINOR
Impact Level
5h 11m
Total Duration
3
Status Updates
Affected Components
OpenTelemetry (Logs, Traces, Metrics)
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed