bgpreport

Network · data from 2026-11-12

AS272004 EGP COMUNICACIONES

Registry name: AS272004 - EGP COMUNICACIONES S.A.C, PE · PeeringDB

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

Announced routes

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

38.43.108.0/24 No ROA Nonecovered by 38.43.108.0/22 671 100% 67
38.43.109.0/24 No ROA Nonecovered by 38.43.108.0/22 671 100% 67
38.43.111.0/24 No ROA Nonecovered by 38.43.108.0/22 671 100% 67
38.158.233.0/24 No ROA Other origin onlycovered by 38.158.232.0/22 671 100% 66
38.158.235.0/24 No ROA Nonecovered by 38.158.232.0/22 671 100% 66
8.243.96.128/27 No ROA None 2 0%low visibility 2
8.243.97.192/26 No ROA None 2 0%low visibility 2
8.243.113.160/27 No ROA None 2 0%low visibility 2
38.43.110.0/24 No ROA Nonecovered by 38.43.108.0/22 2 0%low visibility 2
38.158.234.0/24 No ROA Other IRR onlyRADB 672 100% 67
2803:6910::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS272004'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 24 are in fix.csv.

  • ROA: none10
  • Route object: none9
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none38.43.108.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.671 of 673
Route object: none38.43.108.0/24No route object for it. A route object for 38.43.108.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.671 of 673
ROA: none38.43.109.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.671 of 673
Route object: none38.43.109.0/24No route object for it. A route object for 38.43.108.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.671 of 673
ROA: none38.43.111.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.671 of 673
Route object: none38.43.111.0/24No route object for it. A route object for 38.43.108.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.671 of 673
ROA: none38.158.233.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.671 of 673
Route object: none38.158.233.0/24Route objects for it name AS272836. A route object for 38.158.232.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.671 of 673
ROA: none38.158.235.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.671 of 673
Route object: none38.158.235.0/24No route object for it. A route object for 38.158.232.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.671 of 673
ROA: none8.243.96.128/27No ROA covers it. Add a ROA for AS272004, maxLength 27.2 of 673
Route object: none8.243.96.128/27No route object for it. Add a route object with origin AS272004 in the RIR database for the space.2 of 673
ROA: none8.243.97.192/26No ROA covers it. Add a ROA for AS272004, maxLength 26.2 of 673
Route object: none8.243.97.192/26No route object for it. Add a route object with origin AS272004 in the RIR database for the space.2 of 673
ROA: none8.243.113.160/27No ROA covers it. Add a ROA for AS272004, maxLength 27.2 of 673
Route object: none8.243.113.160/27No route object for it. Add a route object with origin AS272004 in the RIR database for the space.2 of 673
ROA: none38.43.110.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.2 of 673
Route object: none38.43.110.0/24No route object for it. A route object for 38.43.108.0/22 with origin AS272004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272004 in the RIR database for the space.2 of 673
ROA: none38.158.234.0/24No ROA covers it. Add a ROA for AS272004, maxLength 24.672 of 673
Route object: RIR38.158.234.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.43.108.0/22RADBNo ROA
38.158.232.0/22RADBNo ROA
38.255.104.0/21RADBNo ROA
2803:f080:c000::/35LACNICValid

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.