bgpreport

Network · data from 2026-11-12

AS28451 Ignacio Sanchez Gutierrez

Registry name: AS28451 - ASESPRI ETHERNET, MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28451, 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.4.228.0/24 Valid Other IRR onlyRADB 672 100% 66
38.4.229.0/24 Valid Other IRR onlyRADB 672 100% 66
38.4.230.0/24 Valid Other IRR onlyRADB 672 100% 66
38.4.231.0/24 Valid Other IRR onlyRADB 672 100% 66
38.56.248.0/24 Valid Other IRR onlyRADB 671 100% 66
38.56.249.0/24 Valid Other IRR onlyRADB 671 100% 66
38.56.250.0/24 Valid Other IRR onlyRADB 671 100% 66
38.56.251.0/24 Valid Other IRR onlyRADB 671 100% 66
185.240.166.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
2806:3f9::/34 Valid RIR databaseLACNIC, RADB 635 100% 67
2806:3f9:4400::/38 Valid RIR databaseLACNIC, RADB 635 100% 67
2806:3f9:8000::/34 Valid RIR databaseLACNIC, RADB 635 100% 67
2806:3f9:c000::/34 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

AS28451'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 31 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
Route object: RIR38.4.228.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.4.229.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.4.230.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.4.231.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.56.248.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.56.249.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.56.250.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.56.251.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

38.4.228.0/22ARIN, RADBValid
38.4.228.0/23RADBValid
38.4.230.0/23RADBValid
38.56.248.0/22ARINValid
38.56.248.0/23RADBValid
38.56.250.0/23RADBValid
2806:3f9::/32LACNIC, RADBValid
2806:3f9:4000::/34LACNIC, RADBValid
2806:3f9:4000::/38LACNIC, RADBValid
2806:3f9:4800::/38LACNIC, RADBValid
2806:3f9:4c00::/38LACNICValid
2806:3f9:5000::/38LACNICValid
2806:3f9:5400::/38LACNICValid
2806:3f9:5800::/38LACNICValid
2806:3f9:5c00::/38LACNICValid
2806:3f9:6000::/38LACNICValid
2806:3f9:6400::/38LACNICValid
2806:3f9:6800::/38LACNICValid
2806:3f9:6c00::/38LACNICValid
2806:3f9:7000::/38LACNICValid
2806:3f9:7400::/38LACNICValid
2806:3f9:7800::/38LACNICValid
2806:3f9:7c00::/38LACNICValid

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.