ULN-IX: operator report
Ulyanovsk, Russia · PeeringDB 340 · ixreport.com/ix/340/report/
Members of ULN-IX that PeeringDB has wrong, from its IX-F export (12 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 9 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 (9)
These networks could add ULN-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS8402 Corbina Telecom | IX-F | 185.1.19.22 | No public contact |
| AS9049 ER-Telecom | IX-F | 185.1.19.23 2001:7f8:7d::2359:1 |
No public contact |
| AS15774 ULTTK | IX-F | 185.1.19.27 2001:7f8:7d::ab06:1 |
No PeeringDB record |
| AS31138 IPTK | IX-F | 185.1.19.25 2001:7f8:7d::79a2:1 |
No PeeringDB record |
| AS42909 CommunityDNS Ltd | IX-F | 185.1.19.11 2001:7f8:7d::a79d:1 |
No public contact |
| AS48148 SAINF | IX-F | 185.1.19.34 | No PeeringDB record |
| AS49816 MTS | IX-F | 185.1.19.29 | No PeeringDB record |
| AS50716 EVO | IX-F | 185.1.19.30 2001:7f8:7d::c61c:1 |
No PeeringDB record |
| AS198207 EUL | IX-F | 185.1.19.31 | No PeeringDB record |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 3 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 (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.