Network · data from 2026-11-12
AS62261 MSK-IX-AS Join-stock company "Internet Exchange"MSK-IX"
Registry name: MSK-IX-AS Join-stock company "Internet Exchange"MSK-IX", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62261, 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.
| 2a09:bd00:20::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a09:bd00:30::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a09:bd00:40::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 2a09:bd00:20::/48 | No ROA | RIR databaseRIPE | 16 3%low visibility |
| 2a09:bd00:40::/48 | No ROA | RIR databaseRIPE | 16 3%low visibility |
| 2a09:bd00:30::/48 | No ROA | RIR databaseRIPE | 1 0%low visibility |
| 212.192.230.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.192.234.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.192.236.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.192.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a09:bd00:10::/44 | Valid | RIR databaseRIPE | 636 100% |
| 212.192.230.0/24 | Valid | RIR databaseRIPE | 23 3%low visibility |
| 212.192.231.0/24 | Valid | RIR databaseRIPE | 23 3%low visibility |
| 212.192.236.0/24 | Valid | RIR databaseRIPE | 23 3%low visibility |
| 212.192.237.0/24 | Valid | RIR databaseRIPE | 23 3%low visibility |
| 212.192.233.0/24 | Valid | RIR databaseRIPE | 17 3%low visibility |
| 194.85.28.0/24 | Valid | RIR databaseRIPE | 16 2%low visibility |
| 194.85.29.0/24 | Valid | RIR databaseRIPE | 16 2%low visibility |
| 2a09:bd00:10::/48 | Valid | RIR databaseRIPE | 16 3%low visibility |
AS-SET
AS62261 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.
- ROA: none6
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a09:bd00:20::/44 | No ROA covers it. Add a ROA for AS62261, maxLength 44. |
| ROA: none | 2a09:bd00:30::/44 | No ROA covers it. Add a ROA for AS62261, maxLength 44. |
| ROA: none | 2a09:bd00:40::/44 | No ROA covers it. Add a ROA for AS62261, maxLength 44. |
| ROA: none | 2a09:bd00:20::/48 | No ROA covers it. Add a ROA for AS62261, maxLength 48. |
| ROA: none | 2a09:bd00:40::/48 | No ROA covers it. Add a ROA for AS62261, maxLength 48. |
| ROA: none | 2a09:bd00:30::/48 | No ROA covers it. Add a ROA for AS62261, maxLength 48. |
Route objects not announced
Route objects with origin AS62261 whose prefix no peer sees AS62261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.85.28.0/23 | RIPE | Valid |
| 194.226.134.0/23 | RIPE | No ROA |
| 194.226.134.0/24 | RIPE | No ROA |
| 194.226.135.0/24 | RIPE | No ROA |
| 212.192.232.0/23 | RIPE | Valid |
| 212.192.234.0/24 | RIPE | Valid |
| 212.192.235.0/24 | RIPE | Valid |
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.