bgpreport

Network · data from 2026-11-12

AS30417 BTIG-LLC - BTIG LLC

Registry name: BTIG-LLC - BTIG LLC, US · not in PeeringDB

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

Announced routes

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

154.18.188.0/24 No ROA None 1 0%low visibility 1
209.214.224.0/24 No ROA Other IRR onlyRADB 673 100% 67
64.166.128.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
154.61.144.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.133.137.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.146.48.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
192.64.197.0/24 Valid Nonecovered by 192.64.196.0/23 671 100% 67
64.124.70.0/24 Valid Other IRR onlyRADB 671 100% 67
172.81.7.0/24 Valid RIR databaseARIN 673 100% 67
192.64.196.0/24 Valid RIR databaseARIN 673 100% 67
172.81.4.0/22 Valid RIR databaseARIN, RADB 671 100% 67
172.81.4.0/24 Valid RIR databaseARIN 671 100% 67
172.81.5.0/24 Valid RIR databaseARIN 671 100% 67
172.81.6.0/24 Valid RIR databaseARIN 671 100% 67
199.85.245.0/24 Valid RIR databaseARIN, RADB 671 100% 67
91.208.252.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none154.18.188.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.1 of 673
Route object: none154.18.188.0/24No route object for it. Add a route object with origin AS30417 in the RIR database for the space.1 of 673
ROA: none209.214.224.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.673 of 673
Route object: RIR209.214.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none64.166.128.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.671 of 673
Route object: RIR64.166.128.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none154.61.144.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.671 of 673
Route object: RIR154.61.144.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.133.137.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.670 of 673
Route object: RIR38.133.137.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.146.48.0/24No ROA covers it. Add a ROA for AS30417, maxLength 24.670 of 673
Route object: RIR38.146.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: none192.64.197.0/24No route object for it. A route object for 192.64.196.0/23 with origin AS30417 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30417 in the RIR database for the space.671 of 673
Route object: RIR64.124.70.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

192.64.196.0/23ARIN, RADBValid

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.