Network · data from 2026-11-12
AS18278 CableTV Corporation
Registry name: CC9N - Cable TV Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18278, 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.
| 118.82.48.0/20 | Valid | Other IRR onlyRADB | 673 100% |
| 123.0.64.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 123.0.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 183.91.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 202.151.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 202.231.176.0/20 | Valid | Other IRR onlyRADB | 673 100% |
| 210.251.176.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 103.92.228.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 219.100.108.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 2400:a300::/32 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS18278: AS-CABLETV. 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 (AS18278 isn't in the set, or no route object for AS18278 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 | AS18278 in it | Not covered |
|---|---|---|---|---|---|
| AS-CABLETV | RADB | 5 | 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 10 are in fix.csv.
- Route object: RIR10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 118.82.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.0.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.0.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 183.91.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.151.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.231.176.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.251.176.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.92.228.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.100.108.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:a300::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS18278 is announced.
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.