← Back to LaunchDarkly History
none✓ Resolved
Degraded Observability Ingest
Status
resolved
Duration
1h 2m
Updates
3
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedFri, Feb 20, 2026, 11:05 PM
This incident has been resolved.
monitoringFri, Feb 20, 2026, 10:13 PM
Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.
identifiedFri, Feb 20, 2026, 10:12 PM
We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.
investigatingFri, Feb 20, 2026, 10:02 PM
Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.
📊 TECHNICAL DETAILS
Internal ID
06c31f72-fd5b-4e8f-b269-d8a35fe9e4bb
External ID
3j8cq6p4wcm8
🕐 Started
Fri, Feb 20, 2026, 10:02 PM
🔄 Last Updated
Fri, Feb 20, 2026, 11:05 PM
✓ Resolved
Fri, Feb 20, 2026, 11:05 PM
NONE
Impact Level
1h 2m
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