GTT Communications (AS3257): PeeringDB fix list
AS3257 · peeringdb.com/net/14
4 things to fix in GTT Communications (AS3257)'s PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on GTT Communications (AS3257)'s PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (3)
On the exchange's own member list, but not in GTT Communications (AS3257)'s PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 206.126.225.26 IPv6 2001:504:2f::3257:1 Speed Not published RS peer Not published
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 80.81.196.213 is AS203545 NERZEN BILISIM TEKNOLOJILERI 80.81.196.213 IPv6 address missing from PeeringDB 2001:7f8::cb9:0:3 2001:7f8::cb9:0:1 2001:7f8::cb9:0:3 Port speed differs 100G 100G + 10G An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- Add an entry: IPv4 –, IPv6 2001:7f8::cb9:0:1, speed 10000 (10G), RS peer no.
From ixreport.com/net/3257/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.