Yandex TR: PeeringDB fix list
AS212066
2 things to fix in Yandex TR's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
AS212066 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (1)
On the exchange's own member list, but not in Yandex TR's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.48.48 IPv6 2001:7f8:3f:0:3:3c62:0:1 Speed 10000 Mbps (10G) RS peer Yes
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 185.1.48.48 is AS6775 Fink Telecom Services GmbH 185.1.48.48 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.
From ixreport.com/net/212066/: 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.