Network · data from 2026-11-12
AS11440 NETSVILLE - Netsville, Inc.
Registry name: NETSVILLE - Netsville, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11440, 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.
| 69.55.64.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 2606:c380::/32 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS11440 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 9 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.55.64.0/20 | No ROA covers it. Add a ROA for AS11440, maxLength 20. |
| Route object: RIR | 69.55.64.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:c380::/32 | No ROA covers it. Add a ROA for AS11440, maxLength 32. |
| Route object: RIR | 2606:c380::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11440 whose prefix no peer sees AS11440 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.108.245.0/24 | NTTCOM | No ROA |
| 199.233.211.0/24 | NTTCOM | No ROA |
| 206.27.96.0/23 | NTTCOM | No ROA |
| 206.27.124.0/24 | NTTCOM | No ROA |
| 206.27.126.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.