bgpreport

Network · data from 2026-11-12

AS23786 San-in Cable Vision CO.,LTD(MABLE)

Registry name: MABLE - San-in Cable Vision CO.,LTD, JP · PeeringDB

5IPv4 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
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS23786, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23786, 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.
61.245.192.0/20 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
110.50.0.0/20 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.143.192.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
202.162.112.0/20 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
203.215.224.0/21 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
2401:e300::/32 No ROA Other IRR onlyJPIRR, RADB 636 100% 70

AS-SET

AS23786's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none61.245.192.0/20No ROA covers it. Add a ROA for AS23786, maxLength 20.673 of 673
Route object: RIR61.245.192.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none110.50.0.0/20No ROA covers it. Add a ROA for AS23786, maxLength 20.673 of 673
Route object: RIR110.50.0.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.143.192.0/19No ROA covers it. Add a ROA for AS23786, maxLength 19.673 of 673
Route object: RIR202.143.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.162.112.0/20No ROA covers it. Add a ROA for AS23786, maxLength 20.673 of 673
Route object: RIR202.162.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.215.224.0/21No ROA covers it. Add a ROA for AS23786, maxLength 21.673 of 673
Route object: RIR203.215.224.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none2401:e300::/32No ROA covers it. Add a ROA for AS23786, maxLength 32.636 of 636
Route object: RIR2401:e300::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

133.149.64.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.