KVANT-TELECOM: PeeringDB fix list
AS43727 · peeringdb.com/net/2519
6 things to fix in KVANT-TELECOM's PeeringDB record, from what its exchanges publish: 4 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on KVANT-TELECOM'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 (4)
On the exchange's own member list, but not in KVANT-TELECOM's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.170.87 IPv6 2001:7f8:9e::aacf:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 185.1.210.100 IPv6 2001:7f8:3d::aacf:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 185.1.208.94 IPv6 2001:7f8:44::aacf:0:1 Speed 20000 Mbps (20G) RS peer Yes -
IPv4 178.18.226.11 IPv6 2a03:5f80:4::226:11 Speed 100000 Mbps (100G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (2)
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 20G - In the entry with IPv4 80.81.194.124: set Speed to 20000 (20G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.1.222.128: set Speed to 10000 (10G) (now 100000).
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/43727/: 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.