Network · data from 2026-11-12
AS18150 SNI
Registry name: SNI-JP - NetComBB Co.,Ltd., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18150, 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.
| 61.7.0.0/17 | No ROA | Other IRR onlyJPIRR, RADB | 673 100% |
| 61.7.0.0/18 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.7.64.0/18 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.7.64.0/19 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 61.7.0.0/19 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 672 100% |
| 61.7.32.0/19 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 175 26% |
| 61.7.104.0/22 | No ROA | Other IRR onlyJPIRR, NTTCOM, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS18150: AS-SNI-JP. 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 (AS18150 isn't in the set, or no route object for AS18150 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 | AS18150 in it | Not covered |
|---|---|---|---|---|---|
| AS-SNI-JP | RADB | 1 | 1 | Yes | 0 |
| JPIRR (also) | 1 | 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 16 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 61.7.0.0/17 | No ROA covers it. Add a ROA for AS18150, maxLength 17. |
| Route object: RIR | 61.7.0.0/17 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.0.0/18 | No ROA covers it. Add a ROA for AS18150, maxLength 18. |
| Route object: RIR | 61.7.0.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.64.0/18 | No ROA covers it. Add a ROA for AS18150, maxLength 18. |
| Route object: RIR | 61.7.64.0/18 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.64.0/19 | No ROA covers it. Add a ROA for AS18150, maxLength 19. |
| Route object: RIR | 61.7.64.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.0.0/19 | No ROA covers it. Add a ROA for AS18150, maxLength 19. |
| Route object: RIR | 61.7.0.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.32.0/19 | No ROA covers it. Add a ROA for AS18150, maxLength 19. |
| Route object: RIR | 61.7.32.0/19 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 61.7.104.0/22 | No ROA covers it. Add a ROA for AS18150, maxLength 22. |
| Route object: RIR | 61.7.104.0/22 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18150 whose prefix no peer sees AS18150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.7.96.0/19 | JPIRR, NTTCOM, RADB | No ROA |
| 61.7.106.0/23 | 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.