bgpreport

Network · data from 2026-11-12

AS11159 LAPL-LAPUBLICLIBRARY - Los Angeles Public Library

Registry name: LAPL-LAPUBLICLIBRARY - Los Angeles Public Library, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11159, 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.

137.164.7.158/31 No ROA None 1 0%low visibility 1
205.154.192.134/31 No ROA None 1 0%low visibility 1
64.183.42.0/24 Valid Other IRR onlyRADB 668 99% 68
64.183.43.0/24 Valid Other IRR onlyRADB 668 99% 68
173.196.23.0/24 Valid Other IRR onlyRADB 668 99% 68
173.196.24.0/24 Valid Other IRR onlyRADB 668 99% 68
173.196.25.0/24 Valid Other IRR onlyRADB 668 99% 68
173.196.26.0/24 Valid Other IRR onlyRADB 668 99% 68
173.196.27.0/24 Valid Other IRR onlyRADB 668 99% 68

AS-SET

AS11159 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 11 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none137.164.7.158/31No ROA covers it. Add a ROA for AS11159, maxLength 31.1 of 673
Route object: none137.164.7.158/31No route object for it. Add a route object with origin AS11159 in the RIR database for the space.1 of 673
ROA: none205.154.192.134/31No ROA covers it. Add a ROA for AS11159, maxLength 31.1 of 673
Route object: none205.154.192.134/31No route object for it. Add a route object with origin AS11159 in the RIR database for the space.1 of 673
Route object: RIR64.183.42.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR64.183.43.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR173.196.23.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR173.196.24.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR173.196.25.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR173.196.26.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR173.196.27.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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