Geolocation Data

Compute Geolocation Data
02 May 2022, 23:20 UTC
[closed] As described in our April 7, 2022 deprecation of support notice, a third-party vendor for one of Fastly’s geolocation databases is retiring their legacy geoip database. Fastly engineering team will start performing maintenance as part of the retirement of the legacy geoip.* VCL variables beginning May 9th, 2022 at 16:00 UTC. All Fastly services still using the legacy geolocation variables will be migrated by Fastly to the geolocation database using the client.geo.* variables between May 9th 2022 and May 27th 2022. The two sets of geolocation variables use databases from two different third-party vendors and some variable values differ between the two vendors. Fastly has documented the notable differences between the two sets of variables on our Developer Hub here: Starting May 27th 2022, Fastly will no longer support the legacy geolocation geoip.* VCL variables and all instances of them in Fastly services must be removed by this date. Customers should use the client.geo.* variables for geolocation data in all new and existing Fastly services. Additional details have been emailed to known impacted customers from Fastly Customer Support. If you have any questions or concerns you can contact Fastly’s Support team at
09 May 2022, 14:59 UTC
Maintenance will begin as scheduled in 60 minutes.
09 May 2022, 16:00 UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
27 May 2022, 16:00 UTC
The scheduled maintenance has been completed.
11 January 2021, 17:22 UTC
Geolocation Data
11 January 2021, 17:22 UTC
[closed] We are aware of a possible issue and are working to determine the scope and impact.
11 January 2021, 17:29 UTC
We have become aware of an issue where geolocation data may return blank responses for some customers. Our engineering teams are investigating and will provide more information as soon as possible.
11 January 2021, 17:58 UTC
We are continuing to work on a fix for this issue.
11 January 2021, 18:50 UTC
A mitigation has been identified and is in progress.
11 January 2021, 20:16 UTC
A fix has been implemented and we are monitoring the results.
11 January 2021, 20:46 UTC
This incident has been resolved.