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
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% |
| 2806:36f:1::/48 | Valid | Nonecovered by 2806:36f::/32 | 632 99% |
| 2806:36f:1000::/36 | Valid | Nonecovered by 2806:36f::/32 | 632 99% |
| 2806:36f:1400::/40 | Valid | Nonecovered by 2806:36f::/32 | 632 99% |
| 2806:36f:1f00::/40 | Valid | Nonecovered by 2806:36f::/32 | 630 99% |
| 45.191.52.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 45.191.54.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 45.191.53.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 45.191.55.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 45.191.52.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 2806:36f::/32 | Valid | RIR databaseLACNIC, RADB | 632 99% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2806:36f::/36 | No 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. |
| Route object: none | 2806:36f:1::/48 | No 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. |
| Route object: none | 2806:36f:1000::/36 | No 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. |
| Route object: none | 2806:36f:1400::/40 | No 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. |
| Route object: none | 2806:36f:1f00::/40 | No 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. |
| Route object: RIR | 45.191.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.191.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.191.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.191.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
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.