CompaniesLaunchDarklyIncidents
LaunchDarkly: CORS errors for a small subset of customers
Timeline of updates
- resolved
A small number of customers using the LaunchDarkly JavaScript client side SDK with use cases that involved a single browser session requesting the same LaunchDarkly environment from two or more domains in certain situations experienced CORS errors when initializing the SDK from secondary domains. The impact started on Aug 22 and was mitigated on Aug 26. This issue has now been 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: minor) posted by LaunchDarkly, started 2025-08-27 04:00 UTC, resolved after 0 min, 1 update(s).
- Title
- CORS errors for a small subset of customers
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/kymz9x9cqwv3
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on August 27, 2025LaunchDarkly in August 2025MarkdownJSON