Network · data from 2026-11-12
AS18449 AS18449 - MVS Net, S.A. de C.V.
Registry name: AS18449 - MVS Net, S.A. de C.V., MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18449, 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.
| 201.139.1.0/24 | No ROA | Other origin only | 673 100% |
| 201.139.2.0/24 | No ROA | Other origin only | 673 100% |
| 201.139.3.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 201.139.14.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 201.139.11.0/24 | Valid | RIR databaseLACNIC | 2 0%low visibility |
AS-SET
AS18449 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 4 are in fix.csv.
- ROA: none2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 201.139.1.0/24 | No ROA covers it. Add a ROA for AS18449, maxLength 24. |
| Route object: none | 201.139.1.0/24 | Route objects for it name AS8151, AS11172. Add a route object with origin AS18449 in the RIR database for the space. |
| ROA: none | 201.139.2.0/24 | No ROA covers it. Add a ROA for AS18449, maxLength 24. |
| Route object: none | 201.139.2.0/24 | Route objects for it name AS8151, AS11172. Add a route object with origin AS18449 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS18449 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.