bgpreport

Network · data from 2026-11-12

AS265619 XK NET S.A. DE C.V.

Registry name: AS265619 - XK NET S.A. DE C.V., MX · PeeringDB

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

Announced routes

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

2806:36f::/36 Valid Nonecovered by 2806:36f::/32 632 99% 67
2806:36f:1::/48 Valid Nonecovered by 2806:36f::/32 632 99% 67
2806:36f:1000::/36 Valid Nonecovered by 2806:36f::/32 632 99% 67
2806:36f:1400::/40 Valid Nonecovered by 2806:36f::/32 632 99% 67
2806:36f:1f00::/40 Valid Nonecovered by 2806:36f::/32 630 99% 67
45.191.52.0/24 Valid Other IRR onlyRADB 669 99% 67
45.191.54.0/24 Valid Other IRR onlyRADB 669 99% 67
45.191.53.0/24 Valid Other IRR onlyRADB 666 99% 67
45.191.55.0/24 Valid Other IRR onlyRADB 666 99% 67
45.191.52.0/22 Valid RIR databaseLACNIC, RADB 673 100% 67
2806:36f::/32 Valid RIR databaseLACNIC, RADB 632 99% 67

AS-SET

AS265619'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 9 are in fix.csv.

  • Route object: none5
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none2806:36f::/36No route object for it. A route object for 2806:36f::/32 with origin AS265619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265619 in the RIR database for the space.632 of 636
Route object: none2806:36f:1::/48No route object for it. A route object for 2806:36f::/32 with origin AS265619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265619 in the RIR database for the space.632 of 636
Route object: none2806:36f:1000::/36No route object for it. A route object for 2806:36f::/32 with origin AS265619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265619 in the RIR database for the space.632 of 636
Route object: none2806:36f:1400::/40No route object for it. A route object for 2806:36f::/32 with origin AS265619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265619 in the RIR database for the space.632 of 636
Route object: none2806:36f:1f00::/40No route object for it. A route object for 2806:36f::/32 with origin AS265619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265619 in the RIR database for the space.630 of 636
Route object: RIR45.191.52.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.191.54.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.191.53.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.191.55.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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