Network · data from 2026-11-12

AS214083 NODEHUB NodeHub LLC

Registry name: NODEHUB NodeHub LLC, US · not in PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS214083, seen from no peer

Announced routes

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


5.180.234.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.56.38.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.58.170.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.77.108.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.77.208.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.77.210.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.77.213.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
31.77.230.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
82.47.158.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
87.76.147.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
143.20.33.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
151.244.85.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
191.44.102.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
195.58.133.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
77.105.61.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
87.229.22.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
2001:678:db4::/48	Valid	RIR databaseRIPE	634 100%	67
2a13:9500:42::/48	Valid	RIR databaseRIPE	632 99%	67

AS-SET

AS214083 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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