bgpreport

Network · data from 2026-11-12

AS19167 CORE-BROADBAND - Lakeland Networks

Registry name: CORE-BROADBAND - Lakeland Networks, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19167, 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.
204.16.100.0/24 No ROA None 3 0%low visibility 3
204.16.101.0/24 No ROA None 3 0%low visibility 3
204.16.102.0/24 No ROA None 3 0%low visibility 3
204.16.103.0/24 No ROA None 3 0%low visibility 3
204.16.100.0/22 No ROA Other origin only 1 0%low visibility 1

AS-SET

AS19167 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: none5
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none204.16.100.0/24No ROA covers it. Add a ROA for AS19167, maxLength 24.3 of 673
Route object: none204.16.100.0/24No route object for it. Add a route object with origin AS19167 in the RIR database for the space.3 of 673
ROA: none204.16.101.0/24No ROA covers it. Add a ROA for AS19167, maxLength 24.3 of 673
Route object: none204.16.101.0/24No route object for it. Add a route object with origin AS19167 in the RIR database for the space.3 of 673
ROA: none204.16.102.0/24No ROA covers it. Add a ROA for AS19167, maxLength 24.3 of 673
Route object: none204.16.102.0/24No route object for it. Add a route object with origin AS19167 in the RIR database for the space.3 of 673
ROA: none204.16.103.0/24No ROA covers it. Add a ROA for AS19167, maxLength 24.3 of 673
Route object: none204.16.103.0/24No route object for it. Add a route object with origin AS19167 in the RIR database for the space.3 of 673
ROA: none204.16.100.0/22No ROA covers it. Add a ROA for AS19167, maxLength 22.1 of 673
Route object: none204.16.100.0/22Route objects for it name AS5690. Add a route object with origin AS19167 in the RIR database for the space.1 of 673

Route objects not announced

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

192.197.91.0/24RADBNo 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.