Network · data from 2026-11-12
AS23627 UCVNET(Ueda Cable Vision Corporation.)
Registry name: UCVNET - UEDA CABLE VISION CO.,LTD., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23627, 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.
| 113.21.248.0/21 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 116.199.176.0/20 | No ROA | Other IRR onlyJPIRR, RADB | 672 100% |
| 180.200.224.0/21 | No ROA | Other IRR onlyJPIRR | 672 100% |
| 202.213.48.0/20 | No ROA | Other IRR onlyJPIRR, RADB | 672 100% |
| 210.228.16.0/20 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 103.1.252.0/22 | No ROA | Other IRR onlyJPIRR | 670 100% |
| 180.178.88.0/22 | No ROA | Other IRR onlyJPIRR, RADB | 670 100% |
| 2402:bb00::/32 | No ROA | Other IRR onlyJPIRR | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS23627: AS-UCVNET. 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 (AS23627 isn't in the set, or no route object for AS23627 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 | AS23627 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-UCVNET | In no IRR database read today. | |||||
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 19 are in fix.csv.
- ROA: none8
- Route object: RIR8
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 113.21.248.0/21 | No ROA covers it. Add a ROA for AS23627, maxLength 21. |
| Route object: RIR | 113.21.248.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 116.199.176.0/20 | No ROA covers it. Add a ROA for AS23627, maxLength 20. |
| Route object: RIR | 116.199.176.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 180.200.224.0/21 | No ROA covers it. Add a ROA for AS23627, maxLength 21. |
| Route object: RIR | 180.200.224.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 202.213.48.0/20 | No ROA covers it. Add a ROA for AS23627, maxLength 20. |
| Route object: RIR | 202.213.48.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.228.16.0/20 | No ROA covers it. Add a ROA for AS23627, maxLength 20. |
| Route object: RIR | 210.228.16.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.1.252.0/22 | No ROA covers it. Add a ROA for AS23627, maxLength 22. |
| Route object: RIR | 103.1.252.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 180.178.88.0/22 | No ROA covers it. Add a ROA for AS23627, maxLength 22. |
| Route object: RIR | 180.178.88.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 2402:bb00::/32 | No ROA covers it. Add a ROA for AS23627, maxLength 32. |
| Route object: RIR | 2402:bb00::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
| AS-SET: not found | AS-UCVNET | PeeringDB names AS-UCVNET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS23627 whose prefix no peer sees AS23627 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 210.228.16.0/21 | RADB | No ROA |
| 210.228.24.0/22 | RADB | 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.