CompaniesLaunchDarklyIncidents
LaunchDarkly: Retroactive incident: Some audit log entries were not saved
Timeline of updates
- resolved
We have discovered and resolved a problem that caused us to fail to record Audit Log entries. The problem is now corrected. However, between September 7th 11:45 and September 9th 14:40 (PT) the system failed to record the audit log for approximately 2% of Flag Changes. Some audit log entries from this period are missing. Unfortunately, despite our efforts, the missing entries are not recoverable. Additionally, during the period between September 7th 11:45 and September 14th 12:00 (PT) 2.5% of outgoing webhooks used by our integrations also did not send. This problem is also corrected. Note, Flag update and delivery were not affected. The flag changes themselves were made successfully and delivered to users as normal. Only the audit log and webhooks integrations were impacted.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by LaunchDarkly, started 2021-09-17 18:32 UTC, resolved after 0 min, 1 update(s).
- Title
- Retroactive incident: Some audit log entries were not saved
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/wjw1hrws6sjq
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on September 17, 2021LaunchDarkly in September 2021MarkdownJSON