Network · data from 2026-11-12
AS38639 NTT Communications (HANABI)
Registry name: HANABI - NTT DOCOMO BUSINESS, Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38639, 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.
| 115.69.224.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM | 673 100% |
| 220.150.192.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM | 673 100% |
| 220.150.196.0/24 | Valid | Other IRR onlyJPIRR, NTTCOM | 673 100% |
| 103.2.128.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 2402:c800::/32 | Valid | Other IRR onlyJPIRR, NTTCOM | 636 100% |
| 2402:c800:cafe::/48 | Valid | Other IRR onlyJPIRR, NTTCOM | 635 100% |
| 163.138.224.0/19 | Valid | RIR databaseAPNIC, JPIRR, NTTCOM | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS38639: AS-HANABI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS38639 isn't in the set, or no route object for AS38639 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS38639 in it | Not covered |
|---|---|---|---|---|---|
| AS-HANABI | NTTCOM | 7 | 1 | Yes | 0 |
| JPIRR (also) | 7 | 1 | Yes | 0 |
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 8 are in fix.csv.
- Route object: RIR6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 115.69.224.0/21 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 220.150.192.0/21 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 220.150.196.0/24 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.2.128.0/22 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2402:c800::/32 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2402:c800:cafe::/48 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38639 whose prefix no peer sees AS38639 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.138.241.0/24 | APNIC | Valid |
| 163.138.242.0/24 | APNIC | 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.