Virtual Technologies and Solutions: PeeringDB fix list
AS37721 · peeringdb.com/net/17969
4 things to fix in Virtual Technologies and Solutions's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Virtual Technologies and Solutions'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 IPv4 address missing from PeeringDB 185.1.192.178 185.1.192.178 185.1.192.215 IPv6 address missing from PeeringDB 2001:7f8:a0::9359:0:1 2001:7f8:a0::9359:0:1 2001:7f8:a0::9359:0:2 Port speed differs 20G 2 × 100G - In the entry with IPv4 185.1.192.178: set Speed to 100000 (100G) (now 20000).
- Add an entry: IPv4 185.1.192.215, IPv6 2001:7f8:a0::9359:0:2, speed 100000 (100G), RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 2 × 10G 10G 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 1G 10G - In the entry with IPv4 195.66.238.18: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.20.198: set Speed to 12500 (12.5G) (now 100000).
From ixreport.com/net/37721/: 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.