bgpreport

Network · data from 2026-11-12

AS263232 AS263232 - ESPH.SA

Registry name: AS263232 - ESPH.SA, CR · not in PeeringDB

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

Announced routes

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

179.0.208.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.209.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.210.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.211.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.212.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.213.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.214.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.215.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.218.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.219.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.220.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.221.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.222.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.223.0/24 Valid Nonecovered by 179.0.208.0/20 0 0%low visibility 1
179.0.208.0/20 Valid Other IRR onlyRADB 667 99% 68
179.0.216.0/23 Valid Other IRR onlyRADB 667 99% 68
2803:4e80::/32 Valid Other IRR onlyRADB 635 100% 68

AS-SET

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

  • Route object: none14
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none179.0.208.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.209.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.210.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.211.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.212.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.213.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.214.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.215.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.218.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.219.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.220.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.221.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.222.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: none179.0.223.0/24No route object for it. A route object for 179.0.208.0/20 with origin AS263232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263232 in the RIR database for the space.0 of 673
Route object: RIR179.0.208.0/20Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.0.216.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2803:4e80::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS263232 is announced.

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.