GTT Communications IP Ranges
GTT Communications sells IP transit and managed networking, but the backbone people meet in a traceroute is an inherited one. AS3257 is a RIPE object registered on 20 September 2002, held under the name GTT-BACKBONE by ORG-GCI2-RIPE, and PeeringDB still records the same network as formerly Tinet, Inteliquent and Tiscali International Network. Its looking glass, public route server and community list sit on a separate domain, as3257.net, while the peering policy itself is published on gtt.net.
- Provider
- GTT Communications
- Primary ASN
- AS3257
- Category
- Transit
- Headquarters
- McLean, VA, USA
- Announced IPv4 prefixes
- 1382
- Registry
- RIPE
Known IP ranges
These prefixes are currently announced to the global routing table by AS3257 (GTT-BACKBONE GTT Communications Inc.). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
217.204.0.0/14
87.84.0.0/14
82.108.0.0/14
68.164.0.0/14
67.100.0.0/14
66.92.0.0/15
65.84.0.0/15
212.134.0.0/15
66.166.0.0/15
87.84.0.0/15
2a13:fc00::/29
2001:668::/29
2a0a:1f40::/29 (IPv6)
What does a GTT Communications IP mean in a privacy test?
An address on AS3257 that a site records as yours is neither a home broadband line nor a VPN brand. GTT sells transit to networks that resell it: its published peering policy will only consider a peer carrying 100 Gbps in each direction on a 95th percentile basis and providing transit to at least 1500 unique downstream networks, which is the scale of thing that sits behind this number. Because the RIPE record for 82.108.0.0/14 carries a geofeed attribute, the country a lookup reports for that block is a statement GTT filed rather than a guess from latency, and it changes when GTT refiles it. The name whois returns is the thing worth checking, because across much of the European space it is Easynet, a company GTT absorbed, and the country code on that record reads GB no matter where the address is being used. GTT appearing only as an intermediate hop carries no signal at all, since a backbone is meant to be in the path.
What GTT publishes about its own address space
GTT points at its geolocation data from the registry rather than from a support page. The RIPE record for 82.108.0.0/14, netname UK-EASYNET-20031031, carries a geofeed: attribute naming https://geolocation.gtt.net/gtt_geolocation.csv and repeats the same URL in a remark, while the neighbouring allocation 217.204.0.0/14 carries neither, so the attribute is not applied across the whole estate. The file opens with two comment lines, the second of them a generation stamp: the copy read while this page was written said 2026-08-15 00:30:45 +0000. Rows are RFC 8805 five-field records and GTT fills them unevenly, the opening block being country-only as in 194.77.103.0/24,DE,,, while other rows go to city level as in 2001:668:1f:129::/64,NL,NL-NH,Amsterdam,. IPv4 and IPv6 share the one file.
For routing rather than location the objects live on the ASN's own domain. The RIPE as-set AS-GTT, maintained by AS3257-ROUTE-MNT and described only as GTT ASN, contains just AS3257 plus the customer sets AS-GTTCUST and AS-GTTCUST6, so building a prefix filter from it means expanding two further sets first. The community reference is a plain text file at www.as3257.net/communities.txt, which documents 3257:2666 as the blackhole community and warns that GTT has to enable it on a session before it will do anything. None of this identifies a host: the geofeed says where a block is used, the as-set says whose routes GTT will accept, and neither says which machine answered you.
Whose machine is behind a GTT address
Reverse DNS separates GTT's own routers from everything else on the ASN, and it does it in two dialects because the network was assembled out of other companies. Resolved from public DNS while this page was written, 195.66.224.32 answers linx.lon12.ip.tiscali.net and 80.81.196.110 answers ipv4.de-cix.fra.de.as3257.gtt.net, the hostname naming the exchange and the site in each case. A name under ip.tiscali.net or as3257.gtt.net is GTT equipment; a name on an unrelated company's domain, or no PTR at all, is a customer machine sitting in space GTT assigned.
The routing table draws the same line without any DNS. GTT tags a route it originated itself 3257:5000 and a route learned from a transit customer 3257:4000, then stacks a region of origin on top, 3257:50001 for Europe and 3257:50002 for the US and Canada, with city values such as 3257:54901 for Frankfurt. Whois draws it a third way, and this is the one that misleads: 82.108.0.0/14 and 217.204.0.0/14 both belong to ORG-EA49-RIPE, an LIR listed as GTT - EMEA Ltd. at Waterfront House in Nottingham, still maintained by EASYNET-UK-MNT under netnames beginning UK-EASYNET-. The GB country code on those objects describes the registration, not the address in your log.
Related tools
Frequently asked questions
Is AS3257 GTT or Tinet?
Both names describe the same object. The aut-num is registered with RIPE as GTT-BACKBONE, with GTT Communications Inc. as ORG-GCI2-RIPE on the record, and PeeringDB lists the network as formerly Tinet, Inteliquent and Tiscali International Network. The older identity is more than paperwork: GTT's London router at 195.66.224.32 still answers reverse DNS as linx.lon12.ip.tiscali.net.
Does GTT publish a geofeed?
For some of its space. The RIPE record for 82.108.0.0/14 carries a geofeed attribute pointing at geolocation.gtt.net/gtt_geolocation.csv, and the file is stamped with the time it was generated. The neighbouring allocation 217.204.0.0/14 has no such attribute, so do not assume every GTT block is covered, and check the specific record before trusting the feed for an address.
Why does whois on a GTT address return a UK company?
Because GTT grew by acquisition and kept the registry objects it inherited. The RIPE organisation behind two of its largest allocations is ORG-EA49-RIPE, listed as GTT - EMEA Ltd. in Nottingham and still maintained by EASYNET-UK-MNT, with netnames that begin UK-EASYNET. The GB country code there describes the registration, not where the address is being used.
What does GTT require before it will peer with a network?
Its published peering policy asks for at least 100 Gbps of aggregate traffic in each direction, measured on a 95th percentile basis over seven days, a traffic ratio no worse than 3.0 to 1, and transit service to a minimum of 1500 unique downstream networks. The policy sits on gtt.net rather than on as3257.net, which is where the looking glass and community list live.
How do I tell a GTT router from a GTT customer?
Two independent ways. In DNS, GTT's own equipment answers under ip.tiscali.net or as3257.gtt.net and customer machines do not. In BGP, GTT tags its own originated routes 3257:5000 and customer routes 3257:4000, which any public route collector will show you.