bgpreport

Network · data from 2026-11-12

AS273152 MARCO ANTONIO IXCOY VARGAS

Registry name: AS273152 - MARCO ANTONIO IXCOY VARGAS, GT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273152, 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.190.0.0/24 Valid Nonecovered by 38.190.0.0/23 662 98% 68
38.190.1.0/24 Valid Other IRR onlyRADB 669 99% 67
38.190.0.0/23 Valid Other IRR onlyRADB 3 0%low visibility 3
2803:3c50::/32 Valid RIR databaseLACNIC, RADB 629 99% 68

AS-SET

AS273152'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 3 are in fix.csv.

  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none38.190.0.0/24No route object for it. A route object for 38.190.0.0/23 with origin AS273152 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273152 in the RIR database for the space.662 of 673
Route object: RIR38.190.1.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR38.190.0.0/23Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

Every route object with origin AS273152 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.