CompaniesLaunchDarklyIncidents
LaunchDarkly: User indexing is delayed
Snowflake outage, Jun 30, 2021 · 7 vendors, 7 incidents
LaunchDarkly’s incident started in the same window without naming Snowflake (timing only, not evidence of a link). (timing only, posted +32 min vs Snowflake’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Snowflake<br/>posted 18:28 UTC"]:::root
h1["Within an hour<br/>2 vendors, 2 blamed Snowflake<br/>Heap, Lever"]:::blames
root --> h1
me["LaunchDarkly (this incident)<br/>posted +32 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
We've identified an issue with the User Data service. New users are not being indexed and there is an elevated error rate on the user search API. All user data is being queued and will catch up to real-time when the incident is resolved.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
LaunchDarkly profileRecent LaunchDarkly incidentsMarkdownJSON