VASKIANI VENTURES: PeeringDB fix list
AS204453 · peeringdb.com/net/37430
3 things to fix in VASKIANI VENTURES's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on VASKIANI VENTURES'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 (2)
On the exchange's own member list, but not in VASKIANI VENTURES's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (1)
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 89.46.146.46 89.46.146.46 89.46.146.47 IPv6 address missing from PeeringDB none 2001:678:3ac::703 2001:678:3ac::704 Port speed differs 10G 2 × 200G - In the entry with IPv4 89.46.146.46: set IPv6 to 2001:678:3ac::703 (now empty); set Speed to 200000 (200G) (now 10000).
- Add an entry: IPv4 89.46.146.47, IPv6 2001:678:3ac::704, speed 200000 (200G), 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.
From ixreport.com/net/204453/: 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.