bgpreport

Network · data from 2026-11-12

AS43755 NODESDIRECT Nodes Direct Holdings LLC

Registry name: NODESDIRECT Nodes Direct Holdings LLC, US · not in PeeringDB

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

Announced routes

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

208.84.132.0/24 Valid Nonecovered by 208.84.132.0/22 673 100% 67
208.84.135.0/24 Valid Other origin onlycovered by 208.84.132.0/22 672 100% 66
184.175.200.0/22 Valid RIR databaseARIN, RADB 672 100% 66

AS-SET

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

  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none208.84.132.0/24No route object for it. A route object for 208.84.132.0/22 with origin AS43755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43755 in the RIR database for the space.673 of 673
Route object: none208.84.135.0/24Route objects for it name AS19531. A route object for 208.84.132.0/22 with origin AS43755 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43755 in the RIR database for the space.672 of 673

Route objects not announced

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

107.155.128.0/23RADBValid
208.84.132.0/22RADBValid
2604:4600:aa::/48ARINValid

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.