bgpreport

Network · data from 2026-11-12

AS265615 Assetel

Registry name: AS265615 - Assetel SA de CV, MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265615, 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.201.178.0/24 No ROA Other origin only 671 100% 67
38.22.172.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.22.187.0/24 No ROA Other IRR onlyRADB 670 100% 67
201.151.151.0/24 Valid Other IRR onlyRADB 673 100% 67
38.19.94.0/24 Valid Other IRR onlyRADB 672 100% 67
201.151.150.0/24 Valid Other IRR onlyRADB 671 100% 67
38.19.92.0/24 Valid Other IRR onlyRADB 670 100% 67
38.19.93.0/24 Valid Other IRR onlyRADB 670 100% 67
45.190.240.0/22 Valid RIR databaseLACNIC, RADB 673 100% 67
45.190.241.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
45.190.242.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
45.190.243.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
189.206.22.0/24 Valid RIR databaseLACNIC 673 100% 67
201.151.177.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
201.151.178.0/24 Valid RIR databaseLACNIC, RADB 673 100% 67
45.190.240.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
201.151.156.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
201.163.96.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
2806:36c::/32 Valid RIR databaseLACNIC, RADB 635 100% 69

AS-SET

AS265615'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 14 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none189.201.178.0/24No ROA covers it. Add a ROA for AS265615, maxLength 24.671 of 673
Route object: none189.201.178.0/24Route objects for it name AS28438. Add a route object with origin AS265615 in the RIR database for the space.671 of 673
ROA: none38.22.172.0/24No ROA covers it. Add a ROA for AS265615, maxLength 24.672 of 673
Route object: RIR38.22.172.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.22.187.0/24No ROA covers it. Add a ROA for AS265615, maxLength 24.670 of 673
Route object: RIR38.22.187.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.151.151.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.19.94.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.151.150.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR38.19.92.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR38.19.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

38.19.92.0/22ARIN, RADBValid
38.19.95.0/24RADBValid
201.151.150.0/23LACNICValid

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.