Portlane: PeeringDB fix list
AS42708 · peeringdb.com/net/2819
5 things to fix in Portlane's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on Portlane'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 (2)
On the exchange's own member list, but not in Portlane's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.194 IPv6 2001:7f8:d:fb::194 Speed 20000000 Mbps (20T) RS peer No -
IPv4 195.245.240.194 IPv6 2001:7f8:d:fc::194 Speed 20000000 Mbps (20T) RS peer No
Correct these entries (3)
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 20G 20T - In the entry with IPv4 194.68.128.194: set Speed to 20000000 (20T) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 20G 20T - In the entry with IPv4 194.68.123.194: set Speed to 20000000 (20T) (now 20000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 192.121.80.140 192.121.80.116 192.121.80.140 IPv6 address missing from PeeringDB 2001:7f8:3e:0:a500:4:2708:1 2001:7f8:3e:0:a500:4:2708:1 2001:7f8:3e:0:a500:4:2708:2 Port speed differs 100G 2 × 100G - Add an entry: IPv4 192.121.80.116, IPv6 2001:7f8:3e:0:a500:4:2708:2, speed 100000 (100G), RS peer no.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/42708/: 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.