bgpreport

Network · data from 2026-11-12

AS16 LBL - Lawrence Berkeley National Laboratory

Registry name: LBL - Lawrence Berkeley National Laboratory, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16, 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.23.36/31 No ROA None 1 0%low visibility 1
137.164.50.214/31 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:7240/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a43:2d60/123 No ROA None 1 0%low visibility 1
128.3.0.0/16 No ROA Other IRR onlyRADB 670 100% 70
131.243.0.0/16 No ROA Other IRR onlyRADB 670 100% 70
2620:83:8000::/48 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

AS16 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 26 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none137.164.23.36/31No ROA covers it. Add a ROA for AS16, maxLength 31.1 of 673
Route object: none137.164.23.36/31No route object for it. Add a route object with origin AS16 in the RIR database for the space.1 of 673
ROA: none137.164.50.214/31No ROA covers it. Add a ROA for AS16, maxLength 31.1 of 673
Route object: none137.164.50.214/31No route object for it. Add a route object with origin AS16 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:9a41:7240/123No ROA covers it. Add a ROA for AS16, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:7240/123No route object for it. Add a route object with origin AS16 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a43:2d60/123No ROA covers it. Add a ROA for AS16, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a43:2d60/123No route object for it. Add a route object with origin AS16 in the RIR database for the space.1 of 636
ROA: none128.3.0.0/16No ROA covers it. Add a ROA for AS16, maxLength 16.670 of 673
Route object: RIR128.3.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none131.243.0.0/16No ROA covers it. Add a ROA for AS16, maxLength 16.670 of 673
Route object: RIR131.243.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2620:83:8000::/48No ROA covers it. Add a ROA for AS16, maxLength 48.636 of 636
Route object: RIR2620:83:8000::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

128.3.0.0/17RADBNo ROA
128.3.128.0/17RADBNo ROA
131.243.0.0/17RADBNo ROA
131.243.128.0/17RADBNo ROA
2620:83:8000::/46RADBNo ROA
2620:83:8000::/47RADBNo ROA
2620:83:8000::/49RADBNo ROA
2620:83:8000:8000::/49RADBNo ROA
2620:83:8002::/47RADBNo ROA
2620:83:8040::/42RADBNo ROA
2620:83:8040::/43RADBNo ROA
2620:83:8060::/43RADBNo 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.