bgpreport

Network · data from 2026-11-12

AS396882 N3XTWORK

Registry name: N3XTWORK - N3XTWORK LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS396882, 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.
206.166.236.0/24 No ROA RIR databaseARIN 670 100% 68
206.166.237.0/24 No ROA RIR databaseARIN 670 100% 68

AS-SET

AS396882's PeeringDB record names no 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: none2
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none206.166.236.0/24No ROA covers it. Add a ROA for AS396882, maxLength 24.670 of 673
ROA: none206.166.237.0/24No ROA covers it. Add a ROA for AS396882, maxLength 24.670 of 673

Route objects not announced

Route objects with origin AS396882 whose prefix no peer sees AS396882 announce. Many are kept on purpose (backup routes, space announced only in some places).

206.166.224.0/24ARINNo ROA
206.166.225.0/24ARINNo ROA
206.166.226.0/24ARINNo ROA
206.166.227.0/24ARINNo ROA
206.166.228.0/24ARINNo ROA
206.166.229.0/24ARINNo ROA
206.166.230.0/24ARINNo ROA
206.166.231.0/24ARINNo ROA
206.166.232.0/24ARINNo ROA
206.166.233.0/24ARINNo ROA
206.166.234.0/24ARINNo ROA
206.166.235.0/24ARINNo ROA
206.166.238.0/24ARINNo ROA
206.166.239.0/24ARINNo ROA

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.