Korves.Net USA LLC: PeeringDB fix list
AS207439 · peeringdb.com/net/22198
4 things to fix in Korves.Net USA LLC's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Korves.Net USA LLC'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 1G 10G - In the entry with IPv4 185.1.170.222: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 80.81.197.17 80.81.196.251 80.81.197.17 IPv6 address missing from PeeringDB 2001:7f8::3:2a4f:0:2 2001:7f8::3:2a4f:0:1 2001:7f8::3:2a4f:0:2 Port speed differs 500M 100G + 10G - In the entry with IPv4 80.81.197.17: set Speed to 100000 (100G) (now 500).
- Add an entry: IPv4 80.81.196.251, IPv6 2001:7f8::3:2a4f:0:1, speed 10000 (10G), RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.210.194: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.208.200: set Speed to 10000 (10G) (now 1000).
From ixreport.com/net/207439/: 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.