bgpreport

Network · data from 2026-11-12

AS17691 TikiTiki - NDS Co., Ltd.

Registry name: TikiTiki - NDS Co., Ltd., JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17691, 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.4.128.0/20 No ROA Other IRR onlyRADB 672 100% 67
61.4.144.0/21 No ROA Other IRR onlyRADB 672 100% 67
202.157.96.0/22 No ROA Other IRR onlyRADB 672 100% 67
202.157.104.0/21 No ROA Other IRR onlyRADB 672 100% 67
219.117.128.0/20 No ROA Other IRR onlyRADB 672 100% 67
218.40.16.0/20 No ROA Other IRR onlyRADB 671 100% 67
218.223.240.0/20 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS17691 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 28 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none61.4.128.0/20No ROA covers it. Add a ROA for AS17691, maxLength 20.672 of 673
Route object: RIR61.4.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none61.4.144.0/21No ROA covers it. Add a ROA for AS17691, maxLength 21.672 of 673
Route object: RIR61.4.144.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.157.96.0/22No ROA covers it. Add a ROA for AS17691, maxLength 22.672 of 673
Route object: RIR202.157.96.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.157.104.0/21No ROA covers it. Add a ROA for AS17691, maxLength 21.672 of 673
Route object: RIR202.157.104.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none219.117.128.0/20No ROA covers it. Add a ROA for AS17691, maxLength 20.672 of 673
Route object: RIR219.117.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none218.40.16.0/20No ROA covers it. Add a ROA for AS17691, maxLength 20.671 of 673
Route object: RIR218.40.16.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none218.223.240.0/20No ROA covers it. Add a ROA for AS17691, maxLength 20.671 of 673
Route object: RIR218.223.240.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

61.4.128.0/19RADBNo ROA
61.4.144.0/20RADBNo ROA
61.4.152.0/21RADBNo ROA
61.4.152.0/22RADBNo ROA
61.4.156.0/22RADBNo ROA
61.4.160.0/20RADBNo ROA
61.4.160.0/22RADBNo ROA
61.4.164.0/22RADBNo ROA
61.4.168.0/22RADBNo ROA
61.4.172.0/22RADBNo ROA
202.157.96.0/19RADBNo ROA
202.157.103.0/24RADBNo ROA
202.157.112.0/20RADBNo ROA
202.157.124.0/22RADBNo 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.