bgpreport

Network · data from 2026-11-12

AS13614 All West Communications, Inc.

Registry name: ALLWEST - All West Communications, Inc., US · PeeringDB

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

Announced routes

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

38.31.64.0/18 No ROA Other IRR onlyRADB 673 100% 67
162.217.44.0/23 Valid Nonecovered by 162.217.44.0/22 673 100% 67
162.217.46.0/23 Valid Nonecovered by 162.217.44.0/22 673 100% 67
66.205.192.0/19 Valid RIR databaseARIN 673 100% 67
66.205.192.0/20 Valid RIR databaseARIN 673 100% 67
66.205.208.0/20 Valid RIR databaseARIN 673 100% 67
96.43.240.0/20 Valid RIR databaseARIN 673 100% 67
96.43.240.0/21 Valid RIR databaseARIN 673 100% 67
96.43.248.0/21 Valid RIR databaseARIN 673 100% 67
139.60.48.0/20 Valid RIR databaseARIN 673 100% 67
139.60.48.0/22 Valid RIR databaseARIN 673 100% 67
139.60.52.0/22 Valid RIR databaseARIN 673 100% 67
139.60.56.0/22 Valid RIR databaseARIN 673 100% 67
139.60.60.0/22 Valid RIR databaseARIN 673 100% 67
162.216.116.0/22 Valid RIR databaseARIN 673 100% 67
162.216.116.0/23 Valid RIR databaseARIN 673 100% 67
162.216.118.0/23 Valid RIR databaseARIN 673 100% 67
162.217.44.0/22 Valid RIR databaseARIN 673 100% 67
206.217.0.0/20 Valid RIR databaseARIN 673 100% 67
206.217.0.0/21 Valid RIR databaseARIN 673 100% 67
206.217.8.0/21 Valid RIR databaseARIN 673 100% 67
207.135.224.0/19 Valid RIR databaseARIN 673 100% 67
207.135.224.0/20 Valid RIR databaseARIN 673 100% 67
207.135.240.0/20 Valid RIR databaseARIN 673 100% 67
207.135.251.0/24 Valid RIR databaseARIN 673 100% 67
216.117.224.0/20 Valid RIR databaseARIN 673 100% 67
216.117.224.0/21 Valid RIR databaseARIN 673 100% 67
216.117.232.0/21 Valid RIR databaseARIN 673 100% 67
216.250.32.0/20 Valid RIR databaseARIN 673 100% 67
216.250.32.0/21 Valid RIR databaseARIN 673 100% 67
216.250.40.0/21 Valid RIR databaseARIN 673 100% 67
135.129.128.0/18 Valid RIR databaseARIN 670 100% 67
2604:a200::/32 Valid RIR databaseARIN 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS13614: AS-ALLWEST. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS13614 isn't in the set, or no route object for AS13614 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS13614 in itNot covered
AS-ALLWEST ARIN 4135 Yes 0

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

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.31.64.0/18No ROA covers it. Add a ROA for AS13614, maxLength 18.673 of 673
Route object: RIR38.31.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none162.217.44.0/23No route object for it. A route object for 162.217.44.0/22 with origin AS13614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13614 in the RIR database for the space.673 of 673
Route object: none162.217.46.0/23No route object for it. A route object for 162.217.44.0/22 with origin AS13614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13614 in the RIR database for the space.673 of 673

Route objects not announced

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