T2 Rostov-on-Don: PeeringDB fix list
AS42437 · peeringdb.com/net/22153
One thing to fix in T2 Rostov-on-Don's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on T2 Rostov-on-Don'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 (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 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:237 2a03:5f80:4::226:46 - In the entry with IPv4 178.18.224.237: set IPv6 to 2a03:5f80:4::224:237 (now empty).
- In the entry with IPv4 178.18.226.46: set IPv6 to 2a03:5f80:4::226:46 (now empty).
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/42437/: 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.