Network · data from 2026-11-12
AS266774 AS266774 - HIZ TELECOMUNICACIONES S.A.S
Registry name: AS266774 - HIZ TELECOMUNICACIONES S.A.S, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266774, 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.
| 2803:ef20:1007::/48 | Valid | Nonecovered by 2803:ef20::/32 | 636 100% |
| 2803:ef20:100d::/48 | Valid | Nonecovered by 2803:ef20::/32 | 636 100% |
| 2803:ef20:1000::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:1001::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:1002::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:1003::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:1009::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:100a::/48 | Valid | Nonecovered by 2803:ef20::/32 | 635 100% |
| 2803:ef20:1004::/48 | Valid | Nonecovered by 2803:ef20::/32 | 634 100% |
| 2803:ef20:1006::/48 | Valid | Nonecovered by 2803:ef20::/32 | 634 100% |
| 2803:ef20:1008::/48 | Valid | Nonecovered by 2803:ef20::/32 | 634 100% |
| 2803:ef20:1100::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 2803:ef20:1200::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 45.235.42.0/23 | Valid | RIR databaseLACNIC | 671 100% |
| 45.235.43.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 45.235.42.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
AS-SET
AS266774 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 15 are in fix.csv.
- Route object: none11
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:ef20:1007::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:100d::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1000::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1001::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1002::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1003::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1009::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:100a::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1004::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1006::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: none | 2803:ef20:1008::/48 | No route object for it. A route object for 2803:ef20::/32 with origin AS266774 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266774 in the RIR database for the space. |
| Route object: RIR | 2803:ef20:1100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:ef20:1200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266774 whose prefix no peer sees AS266774 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:ef20::/32 | LACNIC | Valid |
| 2803:ef20::/48 | 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.