intersaar: PeeringDB fix list
AS12941 · peeringdb.com/net/4850
5 things to fix in intersaar's PeeringDB record, from what its exchanges publish: 4 to correct, 1 at exchanges that look shut down. As of 2026-10-08 21:56 UTC.
Make the changes on intersaar's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (4)
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 100G - In the entry with IPv4 185.1.170.182: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.210.171: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.245.19: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.208.182: set Speed to 100000 (100G) (now 10000).
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only the operator's own networks
IPv4 185.1.201.1 IPv6 2001:7f8:10d:3ed:0:328d:0:1 Speed 25000 Mbps (25G) IPv4 185.1.201.2 IPv6 2001:7f8:10d:3ed:0:328d:0:2 Speed 25000 Mbps (25G)
From ixreport.com/net/12941/: 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.