Cloudflare: Incorrect geo location for some Cloudflare WARP users
Affected components: WARPZero Trust - WARP
Timeline of updates
- investigating
Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust users being incorrectly geolocated by some third party services.
- identified
The issue has been identified and we are working with third party providers to fix it.
- identified
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- identified
We are continuing to work on a fix for this issue.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
eb3385a8f95f4e49…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fd49b9e2b254acc1…
Impact, status and times are the vendor’s own, as last archived. View on www.cloudflarestatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Cloudflare, started 2026-08-27 18:46 UTC, resolved after 56 d, 9 update(s); edited after publishing.
- Title
- Incorrect geo location for some Cloudflare WARP users
- Vendor
- Cloudflare
- Date
- URL
- https://rewindex.com/company/cloudflare/incidents/9g65dxfbcjln
Cloudflare profileRecent Cloudflare incidentsAll outages on August 27, 2026Cloudflare in August 2026MarkdownJSON