Network · data from 2026-11-12

AS18602 PWRWG - Paul, Weiss, Rifkind, Wharton & Garrison LLP

Registry name: PWRWG - Paul, Weiss, Rifkind, Wharton & Garrison LLP, US · not in PeeringDB

10IPv4 routes 70.0% RPKI valid · 80.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No 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 AS18602, seen from no peer

Announced routes

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


131.239.59.0/24	No ROA	None	673 100%	67
208.226.153.0/24	No ROA	None	673 100%	67
174.47.193.0/24	No ROA	Other IRR onlyRADB	673 100%	67
208.184.158.0/24	Valid	Other IRR onlyRADB	673 100%	66
66.179.116.0/22	Valid	RIR databaseARIN	673 100%	67
66.179.116.0/24	Valid	RIR databaseARIN	673 100%	67
66.179.119.0/24	Valid	RIR databaseARIN	673 100%	67
198.13.254.0/24	Valid	RIR databaseARIN	673 100%	67
66.179.117.0/24	Valid	RIR databaseARIN	672 100%	67
66.179.118.0/24	Valid	RIR databaseARIN	671 100%	67

AS-SET

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

ROA: none3
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	131.239.59.0/24	No ROA covers it. Add a ROA for AS18602, maxLength 24.	673 of 673
Route object: none	131.239.59.0/24	No route object for it. Add a route object with origin AS18602 in the RIR database for the space.	673 of 673
ROA: none	208.226.153.0/24	No ROA covers it. Add a ROA for AS18602, maxLength 24.	673 of 673
Route object: none	208.226.153.0/24	No route object for it. Add a route object with origin AS18602 in the RIR database for the space.	673 of 673
ROA: none	174.47.193.0/24	No ROA covers it. Add a ROA for AS18602, maxLength 24.	673 of 673
Route object: RIR	174.47.193.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	208.184.158.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

131.239.59.0/24

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

673 of 673

Route object: none

131.239.59.0/24

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

673 of 673

ROA: none

208.226.153.0/24

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

673 of 673

Route object: none

208.226.153.0/24

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

673 of 673

ROA: none

174.47.193.0/24

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

673 of 673

Route object: RIR

174.47.193.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

208.184.158.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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