Network · data from 2026-11-12
AS18274 Utsunomiya Cable TV Corporation
Registry name: UCATV - Utsunomiya Cable TV Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18274, 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.
| 116.118.208.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM, RADB | 673 100% |
| 202.173.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM | 673 100% |
| 202.208.64.0/20 | Valid | Other IRR onlyJPIRR | 673 100% |
| 219.97.112.0/21 | Valid | Other IRR onlyJPIRR | 673 100% |
| 219.97.120.0/21 | Valid | Other IRR onlyJPIRR | 673 100% |
| 219.122.96.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM | 673 100% |
| 210.236.112.0/20 | Valid | Other IRR onlyJPIRR, NTTCOM | 672 100% |
| 103.82.88.0/22 | Valid | Other IRR onlyJPIRR | 671 100% |
| 219.100.164.0/22 | Valid | Other IRR onlyJPIRR | 671 100% |
| 2407:3300::/32 | Valid | Other IRR onlyJPIRR | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS18274: JPIRR::AS-UCATV. 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 (AS18274 isn't in the set, or no route object for AS18274 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 | AS18274 in it | Not covered |
|---|---|---|---|---|---|
| JPIRR::AS-UCATV | JPIRR | 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 18 are in fix.csv.
- Route object: RIR10
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 116.118.208.0/20 | Route object only in JPIRR, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.173.96.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.208.64.0/20 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 219.97.112.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 219.97.120.0/21 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 219.122.96.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.236.112.0/20 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.82.88.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.164.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2407:3300::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18274 whose prefix no peer sees AS18274 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 116.118.208.0/21 | JPIRR, NTTCOM | Valid |
| 116.118.216.0/21 | JPIRR, NTTCOM | Valid |
| 202.173.96.0/21 | JPIRR, NTTCOM | Valid |
| 202.173.104.0/21 | JPIRR, NTTCOM | Valid |
| 210.236.112.0/21 | JPIRR, NTTCOM | Valid |
| 210.236.120.0/21 | JPIRR, NTTCOM | Valid |
| 219.122.96.0/21 | JPIRR, NTTCOM | Valid |
| 219.122.104.0/21 | JPIRR, NTTCOM | 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.