bgpreport

Network · data from 2026-11-12

AS1999 HOUSE-AS-1 - U.S. House of Representatives

Registry name: HOUSE-AS-1 - U.S. House of Representatives, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1999, 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.18.0.0/16 No ROA None 673 100% 67
143.228.0.0/16 No ROA None 673 100% 67
143.231.0.0/16 No ROA None 673 100% 67
143.228.193.0/24 No ROA None 672 100% 67
2620:0:e20::/46 No ROA None 635 100% 67
74.119.128.0/24 No ROA RIR databaseARIN 672 100% 67
74.119.130.0/24 No ROA RIR databaseARIN 672 100% 67
74.119.131.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS1999 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 15 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none137.18.0.0/16No ROA covers it. Add a ROA for AS1999, maxLength 16.673 of 673
Route object: none137.18.0.0/16No route object for it. Add a route object with origin AS1999 in the RIR database for the space.673 of 673
ROA: none143.228.0.0/16No ROA covers it. Add a ROA for AS1999, maxLength 16.673 of 673
Route object: none143.228.0.0/16No route object for it. Add a route object with origin AS1999 in the RIR database for the space.673 of 673
ROA: none143.231.0.0/16No ROA covers it. Add a ROA for AS1999, maxLength 16.673 of 673
Route object: none143.231.0.0/16No route object for it. Add a route object with origin AS1999 in the RIR database for the space.673 of 673
ROA: none143.228.193.0/24No ROA covers it. Add a ROA for AS1999, maxLength 24.672 of 673
Route object: none143.228.193.0/24No route object for it. Add a route object with origin AS1999 in the RIR database for the space.672 of 673
ROA: none2620:0:e20::/46No ROA covers it. Add a ROA for AS1999, maxLength 46.635 of 636
Route object: none2620:0:e20::/46No route object for it. Add a route object with origin AS1999 in the RIR database for the space.635 of 636
ROA: none74.119.128.0/24No ROA covers it. Add a ROA for AS1999, maxLength 24.672 of 673
ROA: none74.119.130.0/24No ROA covers it. Add a ROA for AS1999, maxLength 24.672 of 673
ROA: none74.119.131.0/24No ROA covers it. Add a ROA for AS1999, maxLength 24.672 of 673

Route objects not announced

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

74.119.128.0/22ARINNo ROA
74.119.129.0/24ARIN, RADBNo 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.