evo73_MSK: PeeringDB fix list
AS50716
4 things to fix in evo73_MSK's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
AS50716 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (3)
On the exchange's own member list, but not in evo73_MSK's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 178.18.225.252 IPv6 2a03:5f80:4::225:252 Speed 30000 Mbps (30G) RS peer Yes IPv4 178.18.225.36 IPv6 2a03:5f80:4::225:36 Speed 30000 Mbps (30G) 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.
-
IPv4 195.208.211.23 IPv6 2001:7f8:20:101::211:23 Speed Not published 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.
-
IPv4 185.1.19.30 IPv6 2001:7f8:7d::c61c:1 Speed Not published RS peer Not published
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 Address belongs to another network in PeeringDB 195.208.211.23 is AS199651 CLOUDTRANSIT 195.208.211.23 Address belongs to another network in PeeringDB 2001:7f8:20:101::211:23 is AS199651 CLOUDTRANSIT 2001:7f8:20:101::211:23 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
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/50716/: 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.