bgpreport

Network · data from 2026-11-12

AS9618 TCN - catv-tokushima

Registry name: TCN - catv-tokushima, JP · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS9618, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9618, 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.
203.110.96.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
211.19.160.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
2404:2680::/32 No ROA Other IRR onlyJPIRR, RADB 635 100% 70

AS-SET

AS9618 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 10 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none203.110.96.0/19No ROA covers it. Add a ROA for AS9618, maxLength 19.673 of 673
Route object: RIR203.110.96.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.19.160.0/19No ROA covers it. Add a ROA for AS9618, maxLength 19.673 of 673
Route object: RIR211.19.160.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none2404:2680::/32No ROA covers it. Add a ROA for AS9618, maxLength 32.635 of 636
Route object: RIR2404:2680::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS9618 whose prefix no peer sees AS9618 announce. Many are kept on purpose (backup routes, space announced only in some places).

203.110.96.0/20JPIRR, RADBNo ROA
203.110.112.0/20JPIRR, RADBNo ROA
211.19.160.0/20JPIRR, RADBNo ROA
211.19.176.0/20JPIRR, RADBNo 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.