bgpreport

Network · data from 2026-11-12

AS265632 ANGEL BENIGNO CONDOLO GUAYA

Registry name: AS265632 - ANGEL BENIGNO CONDOLO GUAYA, EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265632, 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.
2803:abc0::/47 No ROA Nonecovered by 2803:abc0::/32 635 100% 67
131.196.8.0/24 Valid Nonecovered by 131.196.8.0/22 670 100% 67
131.196.9.0/24 Valid Nonecovered by 131.196.8.0/22 670 100% 67
131.196.10.0/24 Valid Nonecovered by 131.196.8.0/22 670 100% 67
131.196.11.0/24 Valid Nonecovered by 131.196.8.0/22 670 100% 67
2803:abc0::/48 Valid Nonecovered by 2803:abc0::/32 636 100% 67
131.196.8.0/22 Valid Other IRR onlyRADB 667 99% 67

AS-SET

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

  • ROA: none1
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2803:abc0::/47No ROA covers it. Add a ROA for AS265632, maxLength 47.635 of 636
Route object: none2803:abc0::/47No route object for it. A route object for 2803:abc0::/32 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.635 of 636
Route object: none131.196.8.0/24No route object for it. A route object for 131.196.8.0/22 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.670 of 673
Route object: none131.196.9.0/24No route object for it. A route object for 131.196.8.0/22 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.670 of 673
Route object: none131.196.10.0/24No route object for it. A route object for 131.196.8.0/22 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.670 of 673
Route object: none131.196.11.0/24No route object for it. A route object for 131.196.8.0/22 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.670 of 673
Route object: none2803:abc0::/48No route object for it. A route object for 2803:abc0::/32 with origin AS265632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265632 in the RIR database for the space.636 of 636
Route object: RIR131.196.8.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

2803:abc0::/32RADBNo 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.