The automated enhancement provides city-level data for nearly all requests and postal-code information for 90% of platform traffic without requiring manual configuration changes. Because IPs are now evaluated against active network termination points, traffic from hosting providers, VPNs, and leased subnets may reflect different geographical origins than before. Existing geolocation headers and the function helper package will remain consistent, though organizations are advised to test routes tied to localization, compliance, and access controls.
Key points
Visitors connecting through VPNs, hosting providers, and leased IP ranges may now map to…: Visitors connecting through VPNs, hosting providers, and leased IP ranges may now map to different cities or countries.
Underlying geolocation datasets are refreshed more frequently to accurately reflect routi…: Underlying geolocation datasets are refreshed more frequently to accurately reflect routing changes and reassigned IP ranges.
Existing geolocation headers and middleware function helpers will continue to return the…: Existing geolocation headers and middleware function helpers will continue to return the exact same data fields.
Sources checked by our analysis pipeline: 1
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.
Polymarket has reported a major outage affecting its platform. In response to the technical disruption, the prediction market has suspended trading actions.
Robots are scheduled to participate in an upcoming climbing competition at Mount Taishan. The primary objective of the event will be to evaluate the machines' speed as they ascend the mountain. Further details regarding the specific participants, rules, and timeline of the competition have not yet been disclosed.
British regulatory enforcement is under intense scrutiny after official data revealed that statutory duties under the Online Safety Act have failed to reduce minors' exposure to toxic material. Platforms continue pushing violent, self-harm, and pornographic content through personalized algorithms, hitting vulnerable demographics the hardest. The findings amplify public outrage as major tech firms mount legal challenges against existing rules rather than reforming their platform safety designs.