Network · data from 2026-11-12

AS54650 Pathwayz Communications

Registry name: PWZCOM-AMA - Pathwayz Communications, Inc., US · PeeringDB

10IPv4 routes 90.0% RPKI valid · 80.0% 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 AS54650, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS54650, 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.68.2.0/24	No ROA	None	672 100%	67
66.62.146.0/24	Valid	None	673 100%	67
206.166.208.0/24	Valid	RIR databaseARIN	671 100%	67
206.166.209.0/24	Valid	RIR databaseARIN	671 100%	67
206.166.210.0/24	Valid	RIR databaseARIN	671 100%	67
206.166.211.0/24	Valid	RIR databaseARIN	671 100%	67
206.188.200.0/24	Valid	RIR databaseARIN	671 100%	67
206.188.201.0/24	Valid	RIR databaseARIN	671 100%	67
209.172.14.0/24	Valid	RIR databaseARIN	671 100%	67
209.172.15.0/24	Valid	RIR databaseARIN	671 100%	67
2604:bb40::/32	Valid	RIR databaseARIN	635 100%	68

AS-SET

PeeringDB's irr_as_set for AS54650: AS-54650:AS-ALL. 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 (AS54650 isn't in the set, or no route object for AS54650 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.

Name	Database	ASNs	Sets	Route objects	AS54650 in it	Not covered
AS-54650:AS-ALL	ARIN	11	1	28	Yes	2

Name

Database

ASNs

Sets

Route objects

AS54650 in it

Not covered

AS-54650:AS-ALL

ARIN

Yes

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

ROA: none1
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.68.2.0/24	No ROA covers it. Add a ROA for AS54650, maxLength 24.	672 of 673
Route object: none	38.68.2.0/24	No route object for it. Add a route object with origin AS54650 in the RIR database for the space.	672 of 673
Route object: none	66.62.146.0/24	No route object for it. Add a route object with origin AS54650 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.68.2.0/24

No ROA covers it. Add a ROA for AS54650, maxLength 24.

672 of 673

Route object: none

38.68.2.0/24

No route object for it. Add a route object with origin AS54650 in the RIR database for the space.

672 of 673

Route object: none

66.62.146.0/24

No route object for it. Add a route object with origin AS54650 in the RIR database for the space.

673 of 673

Route objects not announced

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