bgpreport

Network · data from 2026-11-12

AS273255 AS273255 - ISIDRO GONZALEZ VASQUEZ

Registry name: AS273255 - ISIDRO GONZALEZ VASQUEZ, MX · not in PeeringDB

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

Announced routes

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

189.204.197.240/28 Invalid: origin None 1 0%low visibility 1
189.204.243.232/29 Invalid: origin None 1 0%low visibility 1
38.211.148.0/24 No ROA Nonecovered by 38.211.148.0/22 672 100% 67
38.211.149.0/24 No ROA Nonecovered by 38.211.148.0/22 672 100% 67
38.211.150.0/24 No ROA Nonecovered by 38.211.148.0/22 672 100% 67
38.211.151.0/24 No ROA Nonecovered by 38.211.148.0/22 671 100% 67
38.211.148.0/22 No ROA Other IRR onlyRADB 670 100% 67
38.9.43.0/24 Valid Nonecovered by 38.9.40.0/22 672 100% 67
38.9.40.0/24 Valid Nonecovered by 38.9.40.0/22 671 100% 67
38.9.42.0/24 Valid Nonecovered by 38.9.40.0/22 669 99% 66
2806:439::/37 Valid Nonecovered by 2806:439::/32 635 100% 67
2806:439::/32 Valid RIR databaseLACNIC, RADB 636 100% 69

AS-SET

AS273255 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 19 are in fix.csv.

  • ROA: origin2
  • ROA: none5
  • Route object: none10
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin189.204.197.240/28ROAs covering it name AS18734, not AS273255. If AS273255 should announce it, add a ROA for AS273255.1 of 673
Route object: none189.204.197.240/28No route object for it. Add a route object with origin AS273255 in the RIR database for the space.1 of 673
ROA: origin189.204.243.232/29ROAs covering it name AS18734, not AS273255. If AS273255 should announce it, add a ROA for AS273255.1 of 673
Route object: none189.204.243.232/29No route object for it. Add a route object with origin AS273255 in the RIR database for the space.1 of 673
ROA: none38.211.148.0/24No ROA covers it. Add a ROA for AS273255, maxLength 24.672 of 673
Route object: none38.211.148.0/24No route object for it. A route object for 38.211.148.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.672 of 673
ROA: none38.211.149.0/24No ROA covers it. Add a ROA for AS273255, maxLength 24.672 of 673
Route object: none38.211.149.0/24No route object for it. A route object for 38.211.148.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.672 of 673
ROA: none38.211.150.0/24No ROA covers it. Add a ROA for AS273255, maxLength 24.672 of 673
Route object: none38.211.150.0/24No route object for it. A route object for 38.211.148.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.672 of 673
ROA: none38.211.151.0/24No ROA covers it. Add a ROA for AS273255, maxLength 24.671 of 673
Route object: none38.211.151.0/24No route object for it. A route object for 38.211.148.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.671 of 673
ROA: none38.211.148.0/22No ROA covers it. Add a ROA for AS273255, maxLength 22.670 of 673
Route object: RIR38.211.148.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none38.9.43.0/24No route object for it. A route object for 38.9.40.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.672 of 673
Route object: none38.9.40.0/24No route object for it. A route object for 38.9.40.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.671 of 673
Route object: none38.9.42.0/24No route object for it. A route object for 38.9.40.0/22 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.669 of 673
Route object: none2806:439::/37No route object for it. A route object for 2806:439::/32 with origin AS273255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273255 in the RIR database for the space.635 of 636

Route objects not announced

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

38.9.40.0/22ARIN, RADBValid

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.