Observability Usage Reporting
Mar 3, 20:40 UTCMar 4, 01:13 UTC
Duration
4h 33m
Impact
Informational
Root cause
Not disclosed
LaunchDarkly, 90 days
16 incidents
Affected
Not listed by the vendor.
Final update
We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.
Timeline
- Resolved · Mar 4, 01:13 UTC
We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.
- Identified · Mar 3, 21:15 UTC
We've identified the root cause affecting the Observability "Errors" usage for some customers and are working to correct it.
- Investigating · Mar 3, 20:40 UTC
We're investigating reports of inaccurate usage reporting for some Observability products.
More from LaunchDarkly
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Aug 2620:00 UTC | Flag delivery errors in Streaming API | minor | 0m |
| Aug 2412:20 UTC | Email delivery failure affecting sign-up verification and notification emails | minor | 1h 15m |
| Aug 1710:36 UTC | Flag Updates via Polling API delayed | minor | 5h 26m |
| Aug 1414:47 UTC | Flag Updates delayed in US Region | minor | 2h |
| Aug 719:29 UTC | Elevated errors on server-side SDK streaming connections | minor | 46m |
| Jul 3117:44 UTC | Investigating - Known Impact | minor | 5h 10m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.