IP geolocation on Vercel now resolves visitor locations with finer network granularity, delivering city-level data for nearly all requests and postal-code data for 90% of traffic. Geolocation data is now refreshed more often, so locations keep up as IP ranges are reassigned and routing changes. This is enabled for all projects with no code or configuration changes required. Existing geolocation headers along with the geolocation() helper in @vercel/functions, return the same fields for Vercel Functions and Routing Middleware. If you use geolocation for access controls, localization, or compliance, some visitors will now resolve to a different city or country, most often traffic from VPNs, hosting providers, and leased IP ranges: Physical termination location: Subnets announced from a hosting provider in a different country than their regional internet registry (RIR) record now resolve to the data center where the traffic actually terminates. Testing geo-dependent routes: Verify access rules against an IP's active network location rather than its static registry allocation. Read the request headers documentation for all available geolocation headers and fields.
AI NEWS JOURNAL
VercelAI NEWS / JOURNAL
IP geolocation now covers more visitors at higher resolution
Vercel now provides city-level geolocation data for nearly all requests and postal-code data for 90% of traffic, with more frequent updates to reflect IP reassignments and routing changes. The improvement is automatic for all projects, requiring no code changes, and applies consistently across Vercel Functions and Routing Middleware. Users relying on geolocation for access controls, localization, or compliance may see shifts in location resolution—particularly for traffic from VPNs, hosting providers, and leased IP ranges—now reflecting the actual physical termination point rather than static registry allocations.