TELE2: PeeringDB fix list
AS1257 · peeringdb.com/net/751
6 things to fix in TELE2's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.
Make the changes on TELE2'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 TELE2's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.21 IPv6 2001:7f8:d:fb::21 Speed Not published RS peer Yes -
IPv4 195.245.240.21 IPv6 2001:7f8:d:fc::21 Speed Not published RS peer Yes -
IPv4 194.68.135.156 IPv6 2001:7f8:d:301::156 Speed Not published RS peer No
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 Port speed differs 100G 100G + 2 × 30G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If TELE2 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 212.237.192.21 IPv6 2001:7f8:d:202::21 Speed 10000 Mbps (10G) -
IPv4 194.68.130.21 IPv6 2001:7f8:d:100::21 Speed 100000 Mbps (100G)
From ixreport.com/net/1257/: 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.