NEAR IP: PeeringDB fix list
AS49600 · peeringdb.com/net/30047
4 things to fix in NEAR IP's PeeringDB record, from what its exchanges publish: 3 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on NEAR IP'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 (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 100G 10G - In the entry with IPv4 193.242.98.169: set Speed to 10000 (10G) (now 100000).
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.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G 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.
-
Problem PeeringDB has The export has Port speed differs 100G 60G - In the entry with IPv4 195.66.224.63: set Speed to 60000 (60G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If NEAR IP has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.0.27.63 IPv6 2001:7f8:15e::63 Speed 100000 Mbps (100G)
From ixreport.com/net/49600/: 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.