bgpreport

Network · data from 2026-11-12

AS11667 WESTEL-ASN1 - Westel, Inc.

Registry name: WESTEL-ASN1 - Westel, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11667, 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.68.141.0/24 No ROA None 672 100% 67
199.68.142.0/24 No ROA None 672 100% 67
199.68.136.0/21 No ROA None 671 100% 67
199.68.140.0/24 No ROA None 671 100% 67
199.68.143.0/24 No ROA None 671 100% 67
204.57.76.0/24 No ROA None 671 100% 67
204.57.84.0/23 No ROA None 671 100% 67
207.71.12.0/23 No ROA None 671 100% 67

AS-SET

AS11667 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none199.68.141.0/24No ROA covers it. Add a ROA for AS11667, maxLength 24.672 of 673
Route object: none199.68.141.0/24No route object for it. Add a route object with origin AS11667 in the RIR database for the space.672 of 673
ROA: none199.68.142.0/24No ROA covers it. Add a ROA for AS11667, maxLength 24.672 of 673
Route object: none199.68.142.0/24No route object for it. Add a route object with origin AS11667 in the RIR database for the space.672 of 673
ROA: none199.68.136.0/21No ROA covers it. Add a ROA for AS11667, maxLength 21.671 of 673
Route object: none199.68.136.0/21No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673
ROA: none199.68.140.0/24No ROA covers it. Add a ROA for AS11667, maxLength 24.671 of 673
Route object: none199.68.140.0/24No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673
ROA: none199.68.143.0/24No ROA covers it. Add a ROA for AS11667, maxLength 24.671 of 673
Route object: none199.68.143.0/24No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673
ROA: none204.57.76.0/24No ROA covers it. Add a ROA for AS11667, maxLength 24.671 of 673
Route object: none204.57.76.0/24No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673
ROA: none204.57.84.0/23No ROA covers it. Add a ROA for AS11667, maxLength 23.671 of 673
Route object: none204.57.84.0/23No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673
ROA: none207.71.12.0/23No ROA covers it. Add a ROA for AS11667, maxLength 23.671 of 673
Route object: none207.71.12.0/23No route object for it. Add a route object with origin AS11667 in the RIR database for the space.671 of 673

Route objects not announced

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