bgpreport

Network · data from 2026-11-12

AS393684 Infinity Network Services

Registry name: INFINITYLINK - Infinity Network Services, Inc., US · PeeringDB

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

Announced routes

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

104.245.184.0/24 Valid Nonecovered by 104.245.184.0/22 673 100% 67
104.245.185.0/24 Valid Nonecovered by 104.245.184.0/22 673 100% 67
104.245.186.0/24 Valid Nonecovered by 104.245.184.0/22 673 100% 67
104.245.187.0/24 Valid Nonecovered by 104.245.184.0/22 673 100% 67
38.83.24.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.25.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.26.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.27.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.28.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.29.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.30.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.31.0/24 Valid Nonecovered by 38.83.24.0/21 672 100% 67
38.83.12.0/24 Valid Other IRR onlyRADB 672 100% 67
38.83.13.0/24 Valid Other IRR onlyRADB 672 100% 67
38.83.14.0/24 Valid Other IRR onlyRADB 672 100% 67
38.83.15.0/24 Valid Other IRR onlyRADB 672 100% 67
23.152.16.0/24 Valid RIR databaseARIN 671 100% 68
38.83.12.0/22 Valid RIR databaseARIN, RADB 671 100% 68
38.83.24.0/21 Valid RIR databaseARIN, RADB 671 100% 68
104.245.184.0/22 Valid RIR databaseARIN, RADB 671 100% 68
2602:ff5f::/36 Valid RIR databaseARIN 635 100% 68
2606:94c0::/32 Valid RIR databaseARIN 635 100% 68
2606:9540::/32 Valid RIR databaseARIN 635 100% 68

AS-SET

AS393684's PeeringDB record names no 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 16 are in fix.csv.

  • Route object: none12
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none104.245.184.0/24No route object for it. A route object for 104.245.184.0/22 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.673 of 673
Route object: none104.245.185.0/24No route object for it. A route object for 104.245.184.0/22 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.673 of 673
Route object: none104.245.186.0/24No route object for it. A route object for 104.245.184.0/22 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.673 of 673
Route object: none104.245.187.0/24No route object for it. A route object for 104.245.184.0/22 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.673 of 673
Route object: none38.83.24.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.25.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.26.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.27.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.28.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.29.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.30.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: none38.83.31.0/24No route object for it. A route object for 38.83.24.0/21 with origin AS393684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393684 in the RIR database for the space.672 of 673
Route object: RIR38.83.12.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.83.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.83.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.83.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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