bgpreport

Network · data from 2026-11-12

AS33174 PRINCE-WILLIAM-COUNTY-VA-ASN - Prince William County Government Department of IT (DoIT)

Registry name: PRINCE-WILLIAM-COUNTY-VA-ASN - Prince William County Government Department of IT (DoIT), US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33174, 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.
2602:fe25:b::/48 No ROA Nonecovered by 2602:fe25::/36 636 100% 68
2602:fe25:a::/48 No ROA Nonecovered by 2602:fe25::/36 635 100% 68
199.34.106.0/24 No ROA RIR databaseARIN 673 100% 70
199.34.107.0/24 No ROA RIR databaseARIN 673 100% 70
216.71.122.0/23 No ROA RIR databaseARIN 673 100% 70
2602:fe25::/36 No ROA RIR databaseARIN 635 100% 68

AS-SET

AS33174 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 9 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2602:fe25:b::/48No ROA covers it. Add a ROA for AS33174, maxLength 48.636 of 636
Route object: none2602:fe25:b::/48No route object for it. A route object for 2602:fe25::/36 with origin AS33174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33174 in the RIR database for the space.636 of 636
ROA: none2602:fe25:a::/48No ROA covers it. Add a ROA for AS33174, maxLength 48.635 of 636
Route object: none2602:fe25:a::/48No route object for it. A route object for 2602:fe25::/36 with origin AS33174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33174 in the RIR database for the space.635 of 636
ROA: none199.34.106.0/24No ROA covers it. Add a ROA for AS33174, maxLength 24.673 of 673
ROA: none199.34.107.0/24No ROA covers it. Add a ROA for AS33174, maxLength 24.673 of 673
ROA: none216.71.122.0/23No ROA covers it. Add a ROA for AS33174, maxLength 23.673 of 673
ROA: none2602:fe25::/36No ROA covers it. Add a ROA for AS33174, maxLength 36.635 of 636

Route objects not announced

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

199.34.106.0/23ARINNo 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.