bgpreport

Network · data from 2026-11-12

AS19076 WELDCOUNTYGOVERNMENT-ASN - Weld County Government

Registry name: WELDCOUNTYGOVERNMENT-ASN - Weld County Government, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19076, 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.133.41.0/24 No ROA None 673 100% 67
204.133.42.0/24 No ROA None 673 100% 67
204.133.43.0/24 No ROA None 673 100% 67
204.133.44.0/24 No ROA None 673 100% 67
204.133.45.0/24 No ROA None 673 100% 67
204.133.46.0/24 No ROA None 673 100% 67
204.133.47.0/24 No ROA None 673 100% 67
204.133.48.0/24 No ROA None 673 100% 67
204.133.49.0/24 No ROA None 673 100% 67
204.133.50.0/24 No ROA None 673 100% 67
204.133.51.0/24 No ROA None 673 100% 67
204.133.52.0/24 No ROA None 673 100% 67
204.133.53.0/24 No ROA None 673 100% 67
204.133.40.0/24 No ROA None 668 99% 67
204.133.39.0/24 Valid None 673 100% 67

AS-SET

AS19076 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 29 are in fix.csv.

  • ROA: none14
  • Route object: none15
ChangePrefix or setDetailFull-table peers
ROA: none204.133.41.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.41.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.42.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.42.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.43.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.43.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.44.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.44.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.45.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.45.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.46.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.46.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.47.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.47.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.48.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.48.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.49.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.49.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.50.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.50.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.51.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.51.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.52.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.52.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.53.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.673 of 673
Route object: none204.133.53.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673
ROA: none204.133.40.0/24No ROA covers it. Add a ROA for AS19076, maxLength 24.668 of 673
Route object: none204.133.40.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.668 of 673
Route object: none204.133.39.0/24No route object for it. Add a route object with origin AS19076 in the RIR database for the space.673 of 673

Route objects not announced

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