Network · data from 2026-11-12
AS41740 NDNS Join-stock company "Internet Exchange"MSK-IX"
Registry name: NDNS Join-stock company "Internet Exchange"MSK-IX", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41740, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 195.208.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.208.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.208.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.208.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.232.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.232.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a09:bd00:3::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:a9c7:9::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:a9c7:b::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:a9c7:147::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:a9c7:253::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:a9c7:8::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:a9c7:a::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:bd00:2::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS41740 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS41740 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.