bgpreport

Network · data from 2026-11-12

AS63331 LBL-2 - Lawrence Berkeley National Laboratory

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63331, 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.38/31 No ROA None 1 0%low visibility 1
137.164.50.250/31 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a41:7260/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a43:2fa0/123 No ROA None 1 0%low visibility 1
192.12.173.0/24 Valid RIR databaseARIN, RADB 670 100% 69
192.58.231.0/24 Valid RIR databaseARIN, RADB 670 100% 69
204.62.155.0/24 Valid RIR databaseARIN, RADB 670 100% 69
2620:83:8004::/47 Valid RIR databaseARIN, RADB 636 100% 70
2620:83:8004::/48 Valid RIR databaseARIN, RADB 636 100% 70
2620:83:8005::/48 Valid RIR databaseARIN, RADB 636 100% 70

AS-SET

AS63331 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: none4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none137.164.23.38/31No ROA covers it. Add a ROA for AS63331, maxLength 31.1 of 673
Route object: none137.164.23.38/31No route object for it. Add a route object with origin AS63331 in the RIR database for the space.1 of 673
ROA: none137.164.50.250/31No ROA covers it. Add a ROA for AS63331, maxLength 31.1 of 673
Route object: none137.164.50.250/31No route object for it. Add a route object with origin AS63331 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:9a41:7260/123No ROA covers it. Add a ROA for AS63331, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a41:7260/123No route object for it. Add a route object with origin AS63331 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a43:2fa0/123No ROA covers it. Add a ROA for AS63331, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a43:2fa0/123No route object for it. Add a route object with origin AS63331 in the RIR database for the space.1 of 636

Route objects not announced

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

2620:83:8080::/43RADBNo ROA
2620:83:8080::/44RADBNo ROA
2620:83:8090::/44RADBNo 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.