bgpreport

Network · data from 2026-11-12

AS8161 INSIGHT-AS - Insight Direct USA, Inc.

Registry name: INSIGHT-AS - Insight Direct USA, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8161, 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.
12.46.160.0/24 No ROA None 673 100% 67
12.46.162.0/23 No ROA None 673 100% 67
12.46.164.0/22 No ROA None 673 100% 67
12.46.165.0/24 No ROA None 673 100% 67
12.46.166.0/24 No ROA None 673 100% 67
12.46.167.0/24 No ROA None 673 100% 67
12.46.168.0/21 No ROA None 673 100% 67
12.46.168.0/24 No ROA None 673 100% 67
208.69.248.0/24 No ROA Nonecovered by 208.69.248.0/23 673 100% 67
12.46.164.0/23 No ROA None 672 100% 67
203.32.108.0/24 No ROA RIR databaseAPNIC 673 100% 68
204.145.196.0/24 No ROA RIR databaseARIN 673 100% 67
208.69.248.0/22 No ROA RIR databaseARIN, RADB 673 100% 67
198.187.200.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
198.206.188.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
199.181.77.0/24 No ROA RIR databaseRIPE 672 100% 67

AS-SET

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

  • ROA: none16
  • Route object: none10
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none12.46.160.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none12.46.160.0/24No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.162.0/23No ROA covers it. Add a ROA for AS8161, maxLength 23.673 of 673
Route object: none12.46.162.0/23No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.164.0/22No ROA covers it. Add a ROA for AS8161, maxLength 22.673 of 673
Route object: none12.46.164.0/22No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.165.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none12.46.165.0/24No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.166.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none12.46.166.0/24No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.167.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none12.46.167.0/24No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.168.0/21No ROA covers it. Add a ROA for AS8161, maxLength 21.673 of 673
Route object: none12.46.168.0/21No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.168.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none12.46.168.0/24No route object for it. Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none208.69.248.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
Route object: none208.69.248.0/24No route object for it. A route object for 208.69.248.0/23 with origin AS8161 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8161 in the RIR database for the space.673 of 673
ROA: none12.46.164.0/23No ROA covers it. Add a ROA for AS8161, maxLength 23.672 of 673
Route object: none12.46.164.0/23No route object for it. Add a route object with origin AS8161 in the RIR database for the space.672 of 673
ROA: none203.32.108.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
ROA: none204.145.196.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.673 of 673
ROA: none208.69.248.0/22No ROA covers it. Add a ROA for AS8161, maxLength 22.673 of 673
ROA: none198.187.200.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.672 of 673
ROA: none198.206.188.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.672 of 673
ROA: none199.181.77.0/24No ROA covers it. Add a ROA for AS8161, maxLength 24.672 of 673

Route objects not announced

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

60.242.125.208/28RADBNo ROA
208.69.248.0/23RADBNo ROA
208.69.250.0/23RADBNo 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.