Network · data from 2026-11-12
AS265584 AS265584 - YAHOO DE MEXICO S.A. DE C.V.
Registry name: AS265584 - YAHOO DE MEXICO S.A. DE C.V., MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265584, 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.
| 45.181.42.0/24 | No ROA | Other origin only | 673 100% |
| 2801:c4:26::/48 | No ROA | Other origin only | 635 100% |
AS-SET
AS265584 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 6 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.181.42.0/24 | No ROA covers it. Add a ROA for AS265584, maxLength 24. |
| Route object: none | 45.181.42.0/24 | Route objects for it name AS8151. Add a route object with origin AS265584 in the RIR database for the space. |
| ROA: none | 2801:c4:26::/48 | No ROA covers it. Add a ROA for AS265584, maxLength 48. |
| Route object: none | 2801:c4:26::/48 | Route objects for it name AS8151. Add a route object with origin AS265584 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265584 whose prefix no peer sees AS265584 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.181.42.0/28 | LACNIC | Valid |
| 2801:c4:26:1::/64 | LACNIC | Valid |
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.