bgpreport

Network · data from 2026-11-12

AS7516 TOHKnet

Registry name: TOHKNET - TOHKnet Co.,Inc., JP · PeeringDB

9IPv4 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
10No 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 AS7516, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7516, 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.
150.30.0.0/16 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
211.2.128.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
211.10.64.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
211.120.96.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
219.109.128.0/19 No ROA Other IRR onlyJPIRR, RADB 673 100% 67
210.175.192.0/19 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
210.239.0.0/19 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
218.216.112.0/20 No ROA Other IRR onlyJPIRR, RADB 672 100% 67
202.254.152.0/24 No ROA Other IRR onlyJPIRR, RADB 671 100% 67
2001:3c0::/35 No ROA Other IRR onlyJPIRR, RADB 633 100% 70

AS-SET

AS7516'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 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none150.30.0.0/16No ROA covers it. Add a ROA for AS7516, maxLength 16.673 of 673
Route object: RIR150.30.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.2.128.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.673 of 673
Route object: RIR211.2.128.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.10.64.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.673 of 673
Route object: RIR211.10.64.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.120.96.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.673 of 673
Route object: RIR211.120.96.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none219.109.128.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.673 of 673
Route object: RIR219.109.128.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.175.192.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.672 of 673
Route object: RIR210.175.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none210.239.0.0/19No ROA covers it. Add a ROA for AS7516, maxLength 19.672 of 673
Route object: RIR210.239.0.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none218.216.112.0/20No ROA covers it. Add a ROA for AS7516, maxLength 20.672 of 673
Route object: RIR218.216.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.254.152.0/24No ROA covers it. Add a ROA for AS7516, maxLength 24.671 of 673
Route object: RIR202.254.152.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
ROA: none2001:3c0::/35No ROA covers it. Add a ROA for AS7516, maxLength 35.633 of 636
Route object: RIR2001:3c0::/35Route object only in JPIRR, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

211.120.96.0/20JPIRR, RADBNo ROA
211.120.112.0/21JPIRR, RADBNo ROA
211.120.120.0/21JPIRR, RADBNo ROA
218.216.112.0/22JPIRR, 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.