bgpreport

Network · data from 2026-11-12

AS3925 ICO-SV - ICOnetworks

Registry name: ICO-SV - ICOnetworks, US · not in PeeringDB

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

Announced routes

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

144.86.191.0/24 No ROA None 673 100% 67
207.111.213.0/24 No ROA Nonecovered by 207.111.192.0/18 673 100% 67
207.111.192.0/18 No ROA Other IRR onlyRADB 673 100% 67
209.165.196.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.197.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.200.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.207.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.209.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.210.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.211.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.213.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.214.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.215.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.217.0/24 Valid Nonecovered by 209.165.192.0/19 673 100% 67
209.165.193.0/24 Valid Nonecovered by 209.165.192.0/19 672 100% 67
209.165.212.0/24 Valid Nonecovered by 209.165.192.0/19 672 100% 67
192.5.31.0/24 Valid RIR databaseARIN 673 100% 67
209.165.192.0/19 Valid RIR databaseARIN 673 100% 67
209.165.192.0/24 Valid RIR databaseARIN 673 100% 67
209.66.100.0/23 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS3925 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 23 are in fix.csv.

  • ROA: none3
  • Route object: none15
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none144.86.191.0/24No ROA covers it. Add a ROA for AS3925, maxLength 24.673 of 673
Route object: none144.86.191.0/24No route object for it. Add a route object with origin AS3925 in the RIR database for the space.673 of 673
ROA: none207.111.213.0/24No ROA covers it. Add a ROA for AS3925, maxLength 24.673 of 673
Route object: none207.111.213.0/24No route object for it. A route object for 207.111.192.0/18 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
ROA: none207.111.192.0/18No ROA covers it. Add a ROA for AS3925, maxLength 18.673 of 673
Route object: RIR207.111.192.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none209.165.196.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.197.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.200.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.207.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.209.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.210.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.211.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.213.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.214.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.215.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.217.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.673 of 673
Route object: none209.165.193.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.672 of 673
Route object: none209.165.212.0/24No route object for it. A route object for 209.165.192.0/19 with origin AS3925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3925 in the RIR database for the space.672 of 673

Route objects not announced

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

173.214.205.0/24ARINValid
192.41.138.0/23ARINValid
209.165.194.0/24ARINValid
2001:470:38f::/48ARINInvalid: origin

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.