IPinfo is the default IP geolocation provider for all Cloudflare services (CF-
Request Headers, Cloudflare Radar, Cloudflare Workers, WAF etc.)
We would like to share that IPinfo is now the default IP geolocation provider for all services across Cloudflare. This also includes Cloudflare’s widely used IP geolocation information packaged in the request headers.
Available Managed Transforms · Cloudflare Rules docs
Header | Description |
---|---|
CF-IPCountry | Two-letter ISO country code (e.g., US, DE, IN) |
CF-Region | Region or state name (e.g., California) |
CF-Region-Code | Subdivision code (e.g., CA) |
CF-City | City name (e.g., San Francisco) |
CF-Postal-Code | Postal/ZIP code |
CF-Timezone | Local timezone of the visitor |
CF-Continent | Continent code (e.g., NA for North America) |
CF-Latitude, CF-Longitude | Approximate lat/lon coordinates |
This is a significant milestone for both IPinfo and Cloudflare, as Cloudflare will now be equipped with best-in-class IP geolocation data backed by IPinfo’s active measurement-based IP geolocation.
Moving beyond our data, we want to ensure that our Cloudflare users and, by extension, our user community at large, know that we will support all of your IP geolocation data needs.
We encourage our Cloudflare+IPinfo users to submit corrections, feedback, and questions.
Questions and Queries
If you have questions or queries regarding our data, feel free to submit them in our community. Through our community, we can provide long-form answers and collaborate with you and our IPinfo community at large.
We welcome you to reach out to our support team via our support portal.
Corrections
IP geolocation · Cloudflare Network settings docs
For IP geolocation corrections, we encourage Cloudflare users to familiarize themselves with our corrections portal: Incorrect IP Geolocation data update - IPinfo.io.
IPinfo accepts corrections in two formats:
- Individual IP submissions: Perfect for one time submissions
- Bulk corrections via Geofeed: For IP range operator submissions
If you have any issues with your own IP geolocation information, we recommend that you submit your location information with a subnet mask of /32
.
Even though our support team is there to assist you, we recommend you submit corrections via the correction portal to streamline processing.
Invalid or incorrect IP location submissions will not be accepted, and we cannot guarantee that your submissions will be reflected in our database.
Your correction submissions will be evaluated with our plethora of networking, data, and machine learning-driven systems. After the verification step is passed, it would take approximately 1-2 days to reflect in our location database and consequently in Cloudflare’s IP geolocation request headers.
If you have any feedback or questions, feel free to drop a comment below.