bgpreport

Network · data from 2026-11-12

AS19531 Nodes Direct

Registry name: NODESDIRECT - Nodes Direct, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19531, 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.
23.92.95.0/24 Valid Nonecovered by 23.92.80.0/20 671 100% 67
199.48.160.0/23 Valid Nonecovered by 199.48.160.0/21 671 100% 67
199.48.163.0/24 Valid Nonecovered by 199.48.160.0/21 671 100% 67
199.48.164.0/23 Valid Nonecovered by 199.48.160.0/21 671 100% 67
199.48.166.0/23 Valid Nonecovered by 199.48.160.0/21 671 100% 67
23.239.64.0/19 Valid Other IRR onlyRADB 673 100% 67
107.155.128.0/19 Valid Other IRR onlyRADB 673 100% 67
184.175.192.0/18 Valid Other IRR onlyRADB 673 100% 67
23.92.80.0/20 Valid Other IRR onlyRADB 672 100% 67
162.216.152.0/21 Valid Other IRR onlyRADB 672 100% 67
162.216.0.0/22 Valid Other IRR onlyRADB 671 100% 67
208.84.132.0/22 Valid Other IRR onlyRADB 670 100% 67
2604:4600::/28 Valid Other IRR onlyRADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS19531: RADB::AS-NDNX. 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 (AS19531 isn't in the set, or no route object for AS19531 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 objectsAS19531 in itNot covered
RADB::AS-NDNX RADBlists itself further down1 member set in no database: AS-SHANEMCC 3054,332 Yes 0

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

  • Route object: none5
  • Route object: RIR8
  • AS-SET: missing member1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none23.92.95.0/24No route object for it. A route object for 23.92.80.0/20 with origin AS19531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19531 in the RIR database for the space.671 of 673
Route object: none199.48.160.0/23No route object for it. A route object for 199.48.160.0/21 with origin AS19531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19531 in the RIR database for the space.671 of 673
Route object: none199.48.163.0/24No route object for it. A route object for 199.48.160.0/21 with origin AS19531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19531 in the RIR database for the space.671 of 673
Route object: none199.48.164.0/23No route object for it. A route object for 199.48.160.0/21 with origin AS19531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19531 in the RIR database for the space.671 of 673
Route object: none199.48.166.0/23No route object for it. A route object for 199.48.160.0/21 with origin AS19531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19531 in the RIR database for the space.671 of 673
Route object: RIR23.239.64.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR107.155.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR184.175.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR23.92.80.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.216.152.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.216.0.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.84.132.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2604:4600::/28Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: missing memberRADB::AS-NDNXAS-NDNX (RADB) lists AS-SHANEMCC; no IRR database read has it.

Route objects not announced

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

199.48.160.0/21RADBValid
208.84.135.0/24RADBValid
2604:4600::/32RADBValid

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.