bgpreport

Network · data from 2026-11-12

AS266722 AS266722 - AMITEL PERU TELECOMUNICACIONES SAC

Registry name: AS266722 - AMITEL PERU TELECOMUNICACIONES SAC, PE · not in PeeringDB

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

Announced routes

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

181.224.200.0/24 No ROA Nonecovered by 181.224.200.0/22 673 100% 67
181.224.201.0/24 No ROA Nonecovered by 181.224.200.0/22 673 100% 67
181.224.203.0/24 No ROA Nonecovered by 181.224.200.0/22 673 100% 67
2803:e500::/32 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

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

  • ROA: none4
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none181.224.200.0/24No ROA covers it. Add a ROA for AS266722, maxLength 24.673 of 673
Route object: none181.224.200.0/24No route object for it. A route object for 181.224.200.0/22 with origin AS266722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266722 in the RIR database for the space.673 of 673
ROA: none181.224.201.0/24No ROA covers it. Add a ROA for AS266722, maxLength 24.673 of 673
Route object: none181.224.201.0/24No route object for it. A route object for 181.224.200.0/22 with origin AS266722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266722 in the RIR database for the space.673 of 673
ROA: none181.224.203.0/24No ROA covers it. Add a ROA for AS266722, maxLength 24.673 of 673
Route object: none181.224.203.0/24No route object for it. A route object for 181.224.200.0/22 with origin AS266722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266722 in the RIR database for the space.673 of 673
ROA: none2803:e500::/32No ROA covers it. Add a ROA for AS266722, maxLength 32.636 of 636
Route object: RIR2803:e500::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

181.224.200.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.