bgpreport

Network · data from 2026-11-12

AS265590 AS265590 - ABIX TELECOMUNICACIONES S.A. DE C.V.

Registry name: AS265590 - ABIX TELECOMUNICACIONES S.A. DE C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265590, 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.210.68.0/24 No ROA Nonecovered by 38.210.68.0/22 672 100% 67
38.210.69.0/24 No ROA Nonecovered by 38.210.68.0/22 672 100% 67
38.210.70.0/24 No ROA Nonecovered by 38.210.68.0/22 672 100% 67
38.210.71.0/24 No ROA Nonecovered by 38.210.68.0/22 672 100% 67
45.178.72.0/24 Valid RIR databaseLACNIC 673 100% 67
45.178.73.0/24 Valid RIR databaseLACNIC 673 100% 67
45.178.74.0/24 Valid RIR databaseLACNIC 673 100% 67
45.178.75.0/24 Valid RIR databaseLACNIC 673 100% 67
63.245.105.0/24 Valid RIR databaseARIN 673 100% 67
2806:341::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

AS265590 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 10 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.210.68.0/24No ROA covers it. Add a ROA for AS265590, maxLength 24.672 of 673
Route object: none38.210.68.0/24No route object for it. A route object for 38.210.68.0/22 with origin AS265590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265590 in the RIR database for the space.672 of 673
ROA: none38.210.69.0/24No ROA covers it. Add a ROA for AS265590, maxLength 24.672 of 673
Route object: none38.210.69.0/24No route object for it. A route object for 38.210.68.0/22 with origin AS265590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265590 in the RIR database for the space.672 of 673
ROA: none38.210.70.0/24No ROA covers it. Add a ROA for AS265590, maxLength 24.672 of 673
Route object: none38.210.70.0/24No route object for it. A route object for 38.210.68.0/22 with origin AS265590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265590 in the RIR database for the space.672 of 673
ROA: none38.210.71.0/24No ROA covers it. Add a ROA for AS265590, maxLength 24.672 of 673
Route object: none38.210.71.0/24No route object for it. A route object for 38.210.68.0/22 with origin AS265590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265590 in the RIR database for the space.672 of 673

Route objects not announced

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

38.210.68.0/22RADBNo ROA
45.178.72.0/22RADBNo ROA

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.