Geolocation
Fastly provides a variety of geolocation data, allowing the originating geographical location of a request to be determined.
IMPORTANT: IP geolocation information, including data streamed by ourlog streaming service, is intended to be used only in connection with your Fastly services. Use of geolocation data for other purposes may require permission fromDigital Element, our data supplier. For more information see ouroverview of using IP-based geolocation and intelligence.
Theclient.geo. namespace contains the geolocation data we recommend for most use cases. Theclient.as. namespace offers information about the client'sAutonomous System (AS), which is often the end user's Internet Service Provider.
Legacy geolocation datasetLearn more...
IP address used for lookup
The IP address used for the geolocation lookup is automatically populated fromclient.ip by default, but may be overridden explicitly by settingclient.geo.ip_override.
Lossy formats
Geographic variables representing names are available in several formats. Note in particular the*.ascii variables are lossy. These variables have diacritics removed and are normalized to lower case spellings. These*.ascii variables are intended for ease of use as a symbolic string in code (for example, to perform some different action depending on the city name), and are generally inappropriate for presenting to users due to their simplified content.
Absent data
The data is updated periodically, as IP allocations change and various amendments are made. Some variables may be absent for the current data at any given time.
For STRING types, the special value? is used to indicate absent data. These may be normalized to VCL empty strings using theif ternary operator:
if (client.as.name=="?",client.as.name,"");In general values of typeSTRING in VCL may benot set, but this should never occur for the Geolocation variables.
- client.geo.area_code —Telephone area code for the client
- client.geo.city —Alias of
client.geo.city.ascii - client.geo.city.ascii —City name for the client (ASCII-encoded, lowercase)
- client.geo.city.latin1 —City name for the client (Latin-1 encoded)
- client.geo.city.utf8 —City name for the client (UTF-8 encoded)
- client.geo.conn_speed —Client connection speed
- client.geo.conn_type —Client connection type
- client.geo.continent_code —Two-letter continent code for the client
- client.geo.country_code —Two-letter country code for the client
- client.geo.country_code3 —Three-letter country code for the client
- client.geo.country_name —Alias of
client.geo.country_name.ascii - client.geo.country_name.ascii —Country name for the client (ASCII-encoded, lowercase)
- client.geo.country_name.latin1 —Country name for the client (Latin-1 encoded)
- client.geo.country_name.utf8 —Country name for the client (UTF-8 encoded)
- client.geo.gmt_offset —Alias of
client.geo.utc_offset - client.geo.ip_override —Override IP address for geolocation data
- client.geo.latitude —Client latitude
- client.geo.longitude —Client longitude
- client.geo.metro_code —Country-specific metro code for the client
- client.geo.postal_code —Country-specific postal area code for the client
- client.geo.proxy_description —Client proxy description
- client.geo.proxy_type —Client proxy type
- client.geo.region —Alias of
client.geo.region.ascii - client.geo.region.ascii —Country subdivision code for the client (ASCII-encoded, uppercase)
- client.geo.region.latin1 —Country subdivision name for the client (Latin-1 encoded)
- client.geo.region.utf8 —Country subdivision name for the client (UTF-8 encoded)
- client.geo.utc_offset —Time zone offset from UTC for the client
