bgpreport

Network · data from 2026-11-12

AS23509 INVLOCSVC - Inventory Locator Service, LLC

Registry name: INVLOCSVC - Inventory Locator Service, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23509, 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.
63.81.126.0/24 No ROA Other IRR onlyRADB 673 100% 67
68.216.160.0/24 No ROA Other IRR onlyRADB 673 100% 67
68.216.162.0/24 No ROA Other IRR onlyRADB 673 100% 67
97.65.14.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.191.104.0/24 No ROA Other IRR onlyRADB 673 100% 67
65.107.133.0/24 No ROA Other IRR onlyRADB 672 100% 67
68.216.161.0/24 No ROA Other IRR onlyRADB 672 100% 67
209.154.176.0/24 No ROA Other IRR onlyRADB 672 100% 67
67.111.63.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

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

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none63.81.126.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.673 of 673
Route object: RIR63.81.126.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none68.216.160.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.673 of 673
Route object: RIR68.216.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none68.216.162.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.673 of 673
Route object: RIR68.216.162.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none97.65.14.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.673 of 673
Route object: RIR97.65.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.191.104.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.673 of 673
Route object: RIR207.191.104.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.107.133.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.672 of 673
Route object: RIR65.107.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none68.216.161.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.672 of 673
Route object: RIR68.216.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none209.154.176.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.672 of 673
Route object: RIR209.154.176.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none67.111.63.0/24No ROA covers it. Add a ROA for AS23509, maxLength 24.671 of 673
Route object: RIR67.111.63.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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