bgpreport

Network · data from 2026-11-12

AS29727 ARCKANET - ARCKANET

Registry name: ARCKANET - ARCKANET, US · not in PeeringDB

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

Announced routes

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

38.22.32.0/24 No ROA Nonecovered by 38.22.32.0/22 672 100% 67
38.22.33.0/24 No ROA Nonecovered by 38.22.32.0/22 672 100% 67
38.22.34.0/24 No ROA Nonecovered by 38.22.32.0/22 672 100% 67
38.22.35.0/24 No ROA Nonecovered by 38.22.32.0/22 672 100% 67
2604:c5c0:100::/40 No ROA Nonecovered by 2604:c5c0::/32 605 95% 67
2604:c5c0:200::/40 No ROA Nonecovered by 2604:c5c0::/32 605 95% 67
23.156.208.0/24 No ROA Other IRR onlyRADB 673 100% 67
38.101.147.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none38.22.32.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.672 of 673
Route object: none38.22.32.0/24No route object for it. A route object for 38.22.32.0/22 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.672 of 673
ROA: none38.22.33.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.672 of 673
Route object: none38.22.33.0/24No route object for it. A route object for 38.22.32.0/22 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.672 of 673
ROA: none38.22.34.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.672 of 673
Route object: none38.22.34.0/24No route object for it. A route object for 38.22.32.0/22 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.672 of 673
ROA: none38.22.35.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.672 of 673
Route object: none38.22.35.0/24No route object for it. A route object for 38.22.32.0/22 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.672 of 673
ROA: none2604:c5c0:100::/40No ROA covers it. Add a ROA for AS29727, maxLength 40.605 of 636
Route object: none2604:c5c0:100::/40No route object for it. A route object for 2604:c5c0::/32 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.605 of 636
ROA: none2604:c5c0:200::/40No ROA covers it. Add a ROA for AS29727, maxLength 40.605 of 636
Route object: none2604:c5c0:200::/40No route object for it. A route object for 2604:c5c0::/32 with origin AS29727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29727 in the RIR database for the space.605 of 636
ROA: none23.156.208.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.673 of 673
Route object: RIR23.156.208.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.101.147.0/24No ROA covers it. Add a ROA for AS29727, maxLength 24.672 of 673
Route object: RIR38.101.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.22.32.0/22RADBNo ROA
70.40.64.0/18RADBNo ROA
74.221.80.0/20RADBNo ROA
131.72.230.0/24RADBNo ROA
168.194.91.0/24RADBNo ROA
201.159.17.0/24RADBNo ROA
201.159.18.0/24RADBNo ROA
201.159.19.0/24RADBNo ROA
201.159.20.0/24RADBNo ROA
201.159.21.0/24RADBNo ROA
201.159.23.0/24RADBNo ROA
216.173.100.0/24RADBNo ROA
216.173.121.0/24RADBNo ROA
2604:c5c0::/32RADBNo ROA
2806:21a:3000::/40RADBNo 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.