RouteViews: PeeringDB fix list
AS6447 · peeringdb.com/net/3367
23 things to fix in RouteViews's PeeringDB record, from what its exchanges publish: 1 to add, 15 to correct, 7 to check. As of 2026-10-08 20:58 UTC.
Make the changes on RouteViews'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 (1)
On the exchange's own member list, but not in RouteViews's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.72.210.169 IPv6 2001:504:13::210:169 Speed Not published RS peer Not published
Correct these entries (15)
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 10G 100M - In the entry with IPv4 80.249.213.84: set Speed to 100 (100M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 203.159.68.20: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 80.81.192.19: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.82.105.7: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 218.100.54.2: set Speed to 1 (1M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 218.100.76.18: set Speed to 1 (1M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 218.100.54.130: set Speed to 1 (1M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 218.100.78.37: set Speed to 1 (1M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 27.106.192.97: set Speed to 1 (1M) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 218.100.52.52: set Speed to 200000 (200G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 196.223.21.54 none IPv6 address in PeeringDB, not in the export 2001:43f8:60:1::54 none Port speed differs 10G 1G - The entry with IPv4 196.223.21.54, IPv6 2001:43f8:60:1::54 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.225.222: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.237.222: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 206.197.187.28: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 185.1.8.105: set Speed to 200000 (200G) (now 10000).
Check these entries (7)
In PeeringDB, but on none of the exchange's own lists. If RouteViews has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 116.89.244.14 IPv6 2401:fdc0:0:1::6447:1 Speed 1000 Mbps (1G) -
IPv4 103.104.19.143 IPv6 2401:fdc0::6447:1 Speed 1000 Mbps (1G) -
IPv4 196.201.2.119 IPv6 – Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 194.68.128.32 IPv6 2001:7f8:d:fe::32 Speed 10000 Mbps (10G) -
IPv4 195.69.119.32 IPv6 2001:7f8:d:fb::32 Speed 10000 Mbps (10G) -
IPv4 194.68.123.32 IPv6 2001:7f8:d:ff::32 Speed 10000 Mbps (10G) -
IPv4 195.245.240.32 IPv6 2001:7f8:d:fc::32 Speed 10000 Mbps (10G)
From ixreport.com/net/6447/: 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.