bgpreport

Network · data from 2026-11-12

AS1982 Northwest Nexus

Registry name: ASN-NWNEXUS - Northwest Nexus Inc., US · PeeringDB

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

Announced routes

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

204.57.215.0/24 No ROA None 673 100% 67
205.235.128.0/20 No ROA Other IRR onlyRADB 670 100% 67
206.63.0.0/17 No ROA Other IRR onlyRADB 670 100% 67
216.251.96.0/20 No ROA Other IRR onlyRADB 670 100% 67
192.135.191.0/24 No ROA Other IRR onlyRADB 668 99% 67
198.202.20.0/24 No ROA Other IRR onlyRADB 668 99% 67
204.238.107.0/24 No ROA Other IRR onlyRADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS1982: AS-NEXUS. 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 (AS1982 isn't in the set, or no route object for AS1982 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 objectsAS1982 in itNot covered
AS-NEXUS RADB 12181 Yes 1
RIPE (also) 2117 No 7

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none204.57.215.0/24No ROA covers it. Add a ROA for AS1982, maxLength 24.673 of 673
Route object: none204.57.215.0/24No route object for it. Add a route object with origin AS1982 in the RIR database for the space.673 of 673
ROA: none205.235.128.0/20No ROA covers it. Add a ROA for AS1982, maxLength 20.670 of 673
Route object: RIR205.235.128.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none206.63.0.0/17No ROA covers it. Add a ROA for AS1982, maxLength 17.670 of 673
Route object: RIR206.63.0.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none216.251.96.0/20No ROA covers it. Add a ROA for AS1982, maxLength 20.670 of 673
Route object: RIR216.251.96.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none192.135.191.0/24No ROA covers it. Add a ROA for AS1982, maxLength 24.668 of 673
Route object: RIR192.135.191.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none198.202.20.0/24No ROA covers it. Add a ROA for AS1982, maxLength 24.668 of 673
Route object: RIR198.202.20.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none204.238.107.0/24No ROA covers it. Add a ROA for AS1982, maxLength 24.668 of 673
Route object: RIR204.238.107.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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