Network · data from 2026-11-12
AS18072 STREAMWING - NTT DOCOMO BUSINESS, Inc.
Registry name: STREAMWING - NTT DOCOMO BUSINESS, Inc., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18072, 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.
| 219.101.48.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 219.101.49.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 219.101.50.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 219.101.51.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 219.101.63.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
AS-SET
AS18072 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 22 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 219.101.48.0/24 | No ROA covers it. Add a ROA for AS18072, maxLength 24. |
| Route object: RIR | 219.101.48.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 219.101.49.0/24 | No ROA covers it. Add a ROA for AS18072, maxLength 24. |
| Route object: RIR | 219.101.49.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 219.101.50.0/24 | No ROA covers it. Add a ROA for AS18072, maxLength 24. |
| Route object: RIR | 219.101.50.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 219.101.51.0/24 | No ROA covers it. Add a ROA for AS18072, maxLength 24. |
| Route object: RIR | 219.101.51.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 219.101.63.0/24 | No ROA covers it. Add a ROA for AS18072, maxLength 24. |
| Route object: RIR | 219.101.63.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18072 whose prefix no peer sees AS18072 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 219.101.48.0/20 | NTTCOM | No ROA |
| 219.101.52.0/24 | NTTCOM | No ROA |
| 219.101.53.0/24 | NTTCOM | No ROA |
| 219.101.54.0/24 | NTTCOM | No ROA |
| 219.101.55.0/24 | NTTCOM | No ROA |
| 219.101.56.0/24 | NTTCOM | No ROA |
| 219.101.57.0/24 | NTTCOM | No ROA |
| 219.101.58.0/24 | NTTCOM | No ROA |
| 219.101.59.0/24 | NTTCOM | No ROA |
| 219.101.60.0/24 | NTTCOM | No ROA |
| 219.101.61.0/24 | NTTCOM | No ROA |
| 219.101.62.0/24 | NTTCOM | 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.