bgpreport

Network · data from 2026-11-12

AS3597 Fundación InnovaT

Registry name: AS3597 - Fundacion InnovaT, AR · PeeringDB

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

Announced routes

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

168.96.0.0/18 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.0.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.10.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.15.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.64.0/18 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.64.0/20 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.66.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.128.0/18 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.148.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.149.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.192.0/18 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.199.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.240.0/24 Valid Nonecovered by 168.96.240.0/23 4 1%low visibility 3
168.96.248.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.250.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.251.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.255.0/24 Valid Nonecovered by 168.96.0.0/16 4 1%low visibility 3
168.96.1.0/24 Valid Other IRR onlyRADB 102 15% 39
168.96.62.0/24 Valid Other IRR onlyRADB 102 15% 39
168.96.252.0/24 Valid Other IRR onlyRADB 102 15% 39
168.96.0.0/16 Valid RIR databaseLACNIC, RADB 672 100% 66
200.10.202.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS3597: LACNIC::AS3597:AS-INNIXP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS3597 isn't in the set, or no route object for AS3597 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS3597 in itNot covered
LACNIC::AS3597:AS-INNIXP LACNIC 4121 Yes 0

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

  • Route object: none17
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none168.96.0.0/18No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.0.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.10.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.15.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.64.0/18No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.64.0/20No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.66.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.128.0/18No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.148.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.149.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.192.0/18No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.199.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.240.0/24No route object for it. A route object for 168.96.240.0/23 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.248.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.250.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.251.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: none168.96.255.0/24No route object for it. A route object for 168.96.0.0/16 with origin AS3597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3597 in the RIR database for the space.4 of 673
Route object: RIR168.96.1.0/24Route object only in RADB. Add it in the RIR database for the space.102 of 673
Route object: RIR168.96.62.0/24Route object only in RADB. Add it in the RIR database for the space.102 of 673
Route object: RIR168.96.252.0/24Route object only in RADB. Add it in the RIR database for the space.102 of 673

Route objects not announced

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

168.96.7.0/24RADBValid
168.96.152.0/22RADBValid
168.96.200.0/24RADBValid
168.96.240.0/23LACNICValid
168.96.254.0/24RADBValid
199.248.144.0/24LACNICValid
200.0.199.0/24RADBNo ROA
2001:1318::/32LACNICValid

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.