Network · data from 2026-11-12
AS22223 MVTV-AS1 - MVTV Wireless
Registry name: MVTV-AS1 - MVTV Wireless, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22223, 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.
| 184.94.128.0/22 | Valid | Nonecovered by 184.94.128.0/21 | 673 100% |
| 184.94.132.0/22 | Valid | Nonecovered by 184.94.128.0/21 | 673 100% |
| 184.94.140.0/22 | Valid | Nonecovered by 184.94.128.0/20 | 673 100% |
| 139.60.108.0/22 | Valid | Nonecovered by 139.60.104.0/21 | 671 100% |
| 184.94.136.0/22 | Valid | Nonecovered by 184.94.128.0/20 | 671 100% |
| 162.218.40.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 162.218.44.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 139.60.104.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 162.211.12.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 24.159.205.0/24 | Valid | RIR databaseARIN | 671 100% |
| 162.218.40.0/21 | Valid | RIR databaseARIN, RADB | 671 100% |
| 162.218.46.0/23 | Valid | RIR databaseARIN | 671 100% |
| 184.94.128.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 192.69.144.0/22 | Valid | RIR databaseARIN | 671 100% |
| 192.190.206.0/23 | Valid | RIR databaseARIN | 671 100% |
| 198.74.28.0/22 | Valid | RIR databaseARIN | 671 100% |
| 2606:f80::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
AS22223 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 10 are in fix.csv.
- Route object: none5
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 184.94.128.0/22 | No route object for it. A route object for 184.94.128.0/21 with origin AS22223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22223 in the RIR database for the space. |
| Route object: none | 184.94.132.0/22 | No route object for it. A route object for 184.94.128.0/21 with origin AS22223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22223 in the RIR database for the space. |
| Route object: none | 184.94.140.0/22 | No route object for it. A route object for 184.94.128.0/20 with origin AS22223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22223 in the RIR database for the space. |
| Route object: none | 139.60.108.0/22 | No route object for it. A route object for 139.60.104.0/21 with origin AS22223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22223 in the RIR database for the space. |
| Route object: none | 184.94.136.0/22 | No route object for it. A route object for 184.94.128.0/20 with origin AS22223 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22223 in the RIR database for the space. |
| Route object: RIR | 162.218.40.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.218.44.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 139.60.104.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22223 whose prefix no peer sees AS22223 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.60.104.0/21 | ARIN, RADB | Valid |
| 184.94.128.0/21 | RADB | 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.