bgpreport

Network · data from 2026-11-12

AS402267 HADOOPSKY - Hadoopsky LLC

Registry name: HADOOPSKY - Hadoopsky LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402267, 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.
162.141.125.0/24 Invalid: origin Other origin only 4 1%low visibility 3
87.83.87.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
109.64.162.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
144.225.91.0/24 Valid RIR databaseARIN, RADB 672 100% 66
162.141.36.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.65.70.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
79.183.187.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
109.66.94.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
79.176.17.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin162.141.125.0/24ROAs covering it name AS834, not AS402267. If AS402267 should announce it, add a ROA for AS402267.4 of 673
Route object: none162.141.125.0/24Route objects for it name AS834. Add a route object with origin AS402267 in the RIR database for the space.4 of 673

Route objects not announced

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