Network · data from 2026-11-12
AS271332 AS271332 - MS NET
Registry name: AS271332 - MS NET, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271332, 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.
| 200.4.115.0/24 | Valid | Nonecovered by 200.4.112.0/22 | 669 99% |
| 200.4.112.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 200.4.114.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.4.113.0/24 | Valid | Other IRR onlyRADB | 665 99% |
AS-SET
AS271332 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 6 are in fix.csv.
- Route object: none1
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.4.115.0/24 | No route object for it. A route object for 200.4.112.0/22 with origin AS271332 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271332 in the RIR database for the space. |
| Route object: RIR | 200.4.112.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.4.114.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.4.113.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271332 whose prefix no peer sees AS271332 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.4.112.0/22 | NTTCOM, RADB | No ROA |
| 2804:79dc::/32 | NTTCOM, 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.