MSK-IX Kazan: operator report
Kazan, Russia · PeeringDB 398 · ixreport.com/ix/398/report/
Members of MSK-IX Kazan that PeeringDB has wrong, from its IX-F export (7 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 5 networks to follow up.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (3)
These networks could add MSK-IX Kazan to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS2854 Orange Business Services Russia & CIS | IX-F | 194.190.119.11 2001:7f8:20:801::119:11 |
No public contact |
| AS50706 MSK-IX Kazan Route Servers | IX-F | 194.190.119.100 2001:7f8:20:801::119:100 |
No PeeringDB record |
| AS205022 JSC MSK-IX | IX-F | 194.190.119.101 2001:7f8:20:801::119:101 |
No PeeringDB record |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 4 networks in both. Either the network's PeeringDB record or the export is out of date.
None: every network's addresses and port speed match.
In PeeringDB, not on your lists (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.