Network · data from 2026-11-12
AS265607 AS265607 - CONECTARED SA DE CV
Registry name: AS265607 - CONECTARED SA DE CV, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265607, 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.
| 186.26.73.0/24 | Valid | Nonecovered by 186.26.72.0/23 | 673 100% |
| 2806:363:4000::/35 | Valid | Nonecovered by 2806:363:4000::/34 | 634 100% |
| 2806:363:6000::/35 | Valid | Nonecovered by 2806:363:4000::/34 | 634 100% |
| 45.188.110.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.188.108.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.188.109.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.188.111.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 186.26.72.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2806:363::/35 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS265607 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 17 are in fix.csv.
- Route object: none3
- Route object: RIR6
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.26.73.0/24 | No route object for it. A route object for 186.26.72.0/23 with origin AS265607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265607 in the RIR database for the space. |
| Route object: none | 2806:363:4000::/35 | No route object for it. A route object for 2806:363:4000::/34 with origin AS265607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265607 in the RIR database for the space. |
| Route object: none | 2806:363:6000::/35 | No route object for it. A route object for 2806:363:4000::/34 with origin AS265607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265607 in the RIR database for the space. |
| Route object: RIR | 45.188.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.26.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:363::/35 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265607 whose prefix no peer sees AS265607 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.188.108.0/22 | LACNIC | Valid |
| 186.26.72.0/23 | LACNIC | Valid |
| 2806:363::/32 | LACNIC, RADB | Valid |
| 2806:363::/34 | RADB | Valid |
| 2806:363:4000::/34 | RADB | Valid |
| 2806:363:8000::/34 | RADB | Valid |
| 2806:363:8000::/35 | RADB | Valid |
| 2806:363:c000::/34 | RADB | 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.