bgpreport

Network · data from 2026-11-12

AS59129 LogicLinks, Inc.

Registry name: LOGICLINKS - LogicLinks, Inc., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59129, 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.
202.17.49.0/24 No ROA None 486 72% 67
202.17.50.0/24 No ROA None 486 72% 67
202.17.51.0/24 No ROA None 486 72% 67
202.17.52.0/24 No ROA None 486 72% 67
202.17.53.0/24 No ROA None 486 72% 67
202.17.54.0/24 No ROA None 486 72% 67
103.90.16.0/23 No ROA Other IRR onlyJPIRR 669 99% 67
219.100.180.0/23 No ROA Other IRR onlyJPIRR 669 99% 67
219.100.182.0/24 No ROA Other IRR onlyJPIRR 669 99% 67

AS-SET

AS59129'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 18 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none202.17.49.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.49.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none202.17.50.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.50.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none202.17.51.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.51.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none202.17.52.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.52.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none202.17.53.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.53.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none202.17.54.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.486 of 673
Route object: none202.17.54.0/24No route object for it. Add a route object with origin AS59129 in the RIR database for the space.486 of 673
ROA: none103.90.16.0/23No ROA covers it. Add a ROA for AS59129, maxLength 23.669 of 673
Route object: RIR103.90.16.0/23Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none219.100.180.0/23No ROA covers it. Add a ROA for AS59129, maxLength 23.669 of 673
Route object: RIR219.100.180.0/23Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
ROA: none219.100.182.0/24No ROA covers it. Add a ROA for AS59129, maxLength 24.669 of 673
Route object: RIR219.100.182.0/24Route object only in JPIRR. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS59129 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.