bgpreport

Network · data from 2026-11-12

AS394621 Data Holdings

Registry name: DATAHOLDINGS-414-USA - Stack41, llc., US · PeeringDB

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

Announced routes

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

161.38.16.0/24 No ROA Nonecovered by 161.38.16.0/22 673 100% 67
161.38.17.0/24 No ROA Nonecovered by 161.38.16.0/22 673 100% 67
161.38.18.0/24 No ROA Nonecovered by 161.38.16.0/22 673 100% 67
161.38.19.0/24 No ROA Nonecovered by 161.38.16.0/22 673 100% 67
148.59.37.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
148.59.133.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
161.38.16.0/22 No ROA RIR databaseARIN, RADB 673 100% 67
162.223.125.0/24 No ROA RIR databaseARIN 672 100% 67
2604:2240::/32 No ROA RIR databaseARIN, RADB 635 100% 67
50.227.99.0/24 Valid None 663 99% 67
207.166.139.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS394621'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 19 are in fix.csv.

  • ROA: none9
  • Route object: none5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none161.38.16.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
Route object: none161.38.16.0/24No route object for it. A route object for 161.38.16.0/22 with origin AS394621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394621 in the RIR database for the space.673 of 673
ROA: none161.38.17.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
Route object: none161.38.17.0/24No route object for it. A route object for 161.38.16.0/22 with origin AS394621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394621 in the RIR database for the space.673 of 673
ROA: none161.38.18.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
Route object: none161.38.18.0/24No route object for it. A route object for 161.38.16.0/22 with origin AS394621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394621 in the RIR database for the space.673 of 673
ROA: none161.38.19.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
Route object: none161.38.19.0/24No route object for it. A route object for 161.38.16.0/22 with origin AS394621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394621 in the RIR database for the space.673 of 673
ROA: none148.59.37.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
ROA: none148.59.133.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.673 of 673
ROA: none161.38.16.0/22No ROA covers it. Add a ROA for AS394621, maxLength 22.673 of 673
ROA: none162.223.125.0/24No ROA covers it. Add a ROA for AS394621, maxLength 24.672 of 673
ROA: none2604:2240::/32No ROA covers it. Add a ROA for AS394621, maxLength 32.635 of 636
Route object: none50.227.99.0/24No route object for it. Add a route object with origin AS394621 in the RIR database for the space.663 of 673

Route objects not announced

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

66.85.82.0/23RADBNo ROA
192.12.108.0/24RADBNo ROA
206.81.84.0/22RADBNo ROA
2605:1e00::/32RADBNo ROA
2620:70:c000::/48ARINNo 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.