rewindex

CompaniesLaunchDarklyIncidents

LaunchDarkly: User Search is returning 504 Timeout.

No impact listedStatus: resolvedStarted Resolved (24 min)1 updatestatus.launchdarkly.com (opens in new tab)

Timeline of updates

  1. resolved

    This incident is now resolved.

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 2018-04-26 21:39 UTC, resolved after 24 min, 1 update(s).

Title
User Search is returning 504 Timeout.
Vendor
LaunchDarkly
Date
URL
https://rewindex.com/company/launchdarkly/incidents/ycb06k5sqrkx

LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on April 26, 2018LaunchDarkly in April 2018MarkdownJSON