bgpreport

Network · data from 2026-11-12

AS28032 InterNexa Peru

Registry name: AS28032 - INTERNEXA PERU S.A, PE · PeeringDB

3IPv4 routes 33.3% RPKI valid · 33.3% with a route object
13IPv6 routes 100.0% RPKI valid · 7.7% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 14 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS28032, seen from no peer

Announced routes

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

191.97.63.0/24 Invalid: origin None 42 6%low visibility 27
179.1.144.0/20 No ROA None 646 96% 66
2800:650:106::/48 Valid Nonecovered by 2800:650::/32 514 81% 67
2800:650:11f::/48 Valid Nonecovered by 2800:650::/32 514 81% 67
2800:650:102::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:103::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:119::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:11c::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:12a::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:135::/48 Valid Nonecovered by 2800:650::/32 513 81% 67
2800:650:10a::/48 Valid Nonecovered by 2800:650::/32 1 0%low visibility 1
2800:650:10c::/48 Valid Nonecovered by 2800:650::/32 1 0%low visibility 1
2800:650:112::/48 Valid Nonecovered by 2800:650::/32 1 0%low visibility 1
2800:650:137::/48 Valid Nonecovered by 2800:650::/32 1 0%low visibility 1
2800:650::/32 Valid Other IRR onlyRADB 1 0%low visibility 1
200.233.46.0/24 Valid RIR databaseLACNIC, RADB 608 90% 67

AS-SET

AS28032'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 18 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none14
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin191.97.63.0/24ROAs covering it name AS18678, not AS28032. If AS28032 should announce it, add a ROA for AS28032.42 of 673
Route object: none191.97.63.0/24No route object for it. Add a route object with origin AS28032 in the RIR database for the space.42 of 673
ROA: none179.1.144.0/20No ROA covers it. Add a ROA for AS28032, maxLength 20.646 of 673
Route object: none179.1.144.0/20No route object for it. Add a route object with origin AS28032 in the RIR database for the space.646 of 673
Route object: none2800:650:106::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.514 of 636
Route object: none2800:650:11f::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.514 of 636
Route object: none2800:650:102::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:103::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:119::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:11c::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:12a::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:135::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.513 of 636
Route object: none2800:650:10a::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.1 of 636
Route object: none2800:650:10c::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.1 of 636
Route object: none2800:650:112::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.1 of 636
Route object: none2800:650:137::/48No route object for it. A route object for 2800:650::/32 with origin AS28032 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28032 in the RIR database for the space.1 of 636
Route object: RIR2800:650::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

45.230.196.0/22RADBNo 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.