Network · data from 2026-11-12
AS48541 NVKZ-STREAM-AS MTS PJSC
Registry name: NVKZ-STREAM-AS MTS PJSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48541, 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.
| 178.72.104.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 178.72.112.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 109.95.164.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 94.199.76.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 178.72.115.0/24 | No ROA | RIR databaseRIPE | 600 89% |
| 178.72.116.0/24 | No ROA | RIR databaseRIPE | 600 89% |
AS-SET
AS48541 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 11 are in fix.csv.
- ROA: none6
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.72.104.0/21 | No ROA covers it. Add a ROA for AS48541, maxLength 21. |
| ROA: none | 178.72.112.0/20 | No ROA covers it. Add a ROA for AS48541, maxLength 20. |
| ROA: none | 109.95.164.0/22 | No ROA covers it. Add a ROA for AS48541, maxLength 22. |
| ROA: none | 94.199.76.0/22 | No ROA covers it. Add a ROA for AS48541, maxLength 22. |
| ROA: none | 178.72.115.0/24 | No ROA covers it. Add a ROA for AS48541, maxLength 24. |
| ROA: none | 178.72.116.0/24 | No ROA covers it. Add a ROA for AS48541, maxLength 24. |
Route objects not announced
Route objects with origin AS48541 whose prefix no peer sees AS48541 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.72.104.0/24 | RIPE | No ROA |
| 178.72.112.0/21 | RIPE | No ROA |
| 178.72.124.0/23 | RIPE | No ROA |
| 178.72.126.0/24 | RIPE | No ROA |
| 178.72.127.0/24 | RIPE | No ROA |
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.