bgpreport

Network · data from 2026-11-12

AS26045 LUBBCO1 - Lubbock County

Registry name: LUBBCO1 - Lubbock County, US · not in PeeringDB

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

Announced routes

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

199.34.9.0/24 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

AS26045 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 97 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced95
ChangePrefix or setDetailFull-table peers
ROA: none199.34.9.0/24No ROA covers it. Add a ROA for AS26045, maxLength 24.670 of 673
Route object: RIR199.34.9.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

63.141.32.0/22RADBNo ROA
63.141.32.0/23RADBNo ROA
63.141.32.0/24RADBNo ROA
63.141.34.0/23RADBNo ROA
63.141.34.0/24RADBNo ROA
63.141.35.0/24RADBNo ROA
63.141.40.0/21RADBNo ROA
63.141.40.0/22RADBNo ROA
63.141.40.0/23RADBNo ROA
63.141.40.0/24RADBNo ROA
63.141.41.0/24RADBNo ROA
63.141.42.0/23RADBNo ROA
63.141.42.0/24RADBNo ROA
63.141.43.0/24RADBNo ROA
63.141.44.0/22RADBNo ROA
63.141.44.0/23RADBNo ROA
63.141.44.0/24RADBNo ROA
63.141.45.0/24RADBNo ROA
63.141.46.0/23RADBNo ROA
63.141.46.0/24RADBNo ROA
63.141.47.0/24RADBNo ROA
63.141.48.0/21RADBNo ROA
63.141.48.0/22RADBNo ROA
63.141.48.0/23RADBNo ROA
63.141.50.0/23RADBNo ROA
63.141.52.0/23RADBNo ROA
63.141.52.0/24RADBNo ROA
63.141.53.0/24RADBNo ROA
63.141.54.0/23RADBNo ROA
63.141.54.0/24RADBNo ROA
63.141.55.0/24RADBNo ROA
63.141.56.0/23RADBNo ROA
63.141.56.0/24RADBNo ROA
63.141.58.0/23RADBNo ROA
63.141.60.0/22RADBNo ROA
63.141.60.0/23RADBNo ROA
63.141.60.0/24RADBNo ROA
63.141.61.0/24RADBNo ROA
63.141.62.0/23RADBNo ROA
94.154.128.0/19RADBNo ROA
94.154.128.0/20RADBNo ROA
94.154.128.0/21RADBNo ROA
94.154.132.0/22RADBNo ROA
94.154.136.0/21RADBNo ROA
94.154.136.0/22RADBNo ROA
94.154.136.0/23RADBNo ROA
94.154.136.0/24RADBNo ROA
94.154.137.0/24RADBNo ROA
94.154.138.0/23RADBNo ROA
94.154.138.0/24RADBNo ROA
94.154.139.0/24RADBNo ROA
94.154.140.0/22RADBNo ROA
94.154.140.0/23RADBNo ROA
94.154.140.0/24RADBNo ROA
94.154.141.0/24RADBNo ROA
94.154.142.0/23RADBNo ROA
94.154.142.0/24RADBNo ROA
94.154.143.0/24RADBNo ROA
94.154.144.0/20RADBNo ROA
94.154.144.0/21RADBNo ROA
94.154.152.0/21RADBNo ROA
94.154.156.0/22RADBNo ROA
94.154.156.0/23RADBNo ROA
94.154.156.0/24RADBNo ROA
94.154.157.0/24RADBNo ROA
94.154.158.0/23RADBNo ROA
94.154.158.0/24RADBNo ROA
94.154.159.0/24RADBNo ROA
94.154.160.0/20RADBNo ROA
94.154.160.0/21RADBNo ROA
94.154.160.0/22RADBNo ROA
94.154.168.0/21RADBNo ROA
94.154.168.0/22RADBNo ROA
94.154.170.0/23RADBNo ROA
94.154.178.0/23RADBNo ROA
94.154.184.0/21RADBNo ROA
94.154.188.0/22RADBNo ROA
94.154.188.0/23RADBNo ROA
94.154.190.0/23RADBNo ROA
96.126.64.0/23RADBNo ROA
96.126.64.0/24RADBNo ROA
96.126.66.0/23RADBNo ROA
96.126.66.0/24RADBNo ROA
96.126.67.0/24RADBNo ROA
96.126.68.0/23RADBNo ROA
199.58.253.0/24RADBNo ROA
199.58.254.0/24RADBNo ROA
208.117.88.0/22RADBNo ROA
208.117.88.0/23RADBNo ROA
208.117.88.0/24RADBNo ROA
208.117.89.0/24RADBNo ROA
208.117.90.0/23RADBNo ROA
208.117.90.0/24RADBNo ROA
208.117.91.0/24RADBNo ROA
208.117.94.0/23RADBNo 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.