Network · data from 2026-11-12
AS273019 DIRECTV CHILE TELEVISION LIMITADA
Registry name: AS273019 - DIRECTV CHILE TELEVISION LIMITADA, CL · PeeringDB
17IPv4 routes
100.0% RPKI valid · 29.4% with a route object
7IPv6 routes
100.0% RPKI valid · 14.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
18 with no route object for this origin
6Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS273019, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS273019, 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.
| 190.12.168.0/23 | Valid | Nonecovered by 190.12.168.0/22 | 671 100% |
| 190.12.172.0/24 | Valid | Nonecovered by 190.12.172.0/22 | 671 100% |
| 190.12.174.0/24 | Valid | Nonecovered by 190.12.172.0/22 | 671 100% |
| 190.12.168.0/24 | Valid | Nonecovered by 190.12.168.0/22 | 670 100% |
| 190.12.169.0/24 | Valid | Nonecovered by 190.12.168.0/22 | 670 100% |
| 190.12.170.0/24 | Valid | Nonecovered by 190.12.168.0/22 | 670 100% |
| 190.12.171.0/24 | Valid | Nonecovered by 190.12.168.0/22 | 670 100% |
| 190.12.173.0/24 | Valid | Nonecovered by 190.12.172.0/22 | 670 100% |
| 2803:3c90:207::/48 | Valid | Nonecovered by 2803:3c90::/32 | 636 100% |
| 2803:3c90:208::/48 | Valid | Nonecovered by 2803:3c90::/32 | 636 100% |
| 2803:3c90:a00::/39 | Valid | Nonecovered by 2803:3c90::/32 | 636 100% |
| 2803:3c90:c00::/39 | Valid | Nonecovered by 2803:3c90::/32 | 636 100% |
| 190.12.170.0/23 | Valid | Nonecovered by 190.12.168.0/22 | 30 4%low visibility |
| 190.12.172.0/23 | Valid | Nonecovered by 190.12.172.0/22 | 30 4%low visibility |
| 190.12.174.0/23 | Valid | Nonecovered by 190.12.172.0/22 | 30 4%low visibility |
| 190.12.175.0/24 | Valid | Nonecovered by 190.12.172.0/22 | 30 4%low visibility |
| 2803:3c90:a00::/40 | Valid | Nonecovered by 2803:3c90::/32 | 9 1%low visibility |
| 2803:3c90:c00::/40 | Valid | Nonecovered by 2803:3c90::/32 | 9 1%low visibility |
| 190.44.225.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.44.230.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.101.255.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.12.168.0/22 | Valid | RIR databaseLACNIC | 670 100% |
| 190.12.172.0/22 | Valid | RIR databaseLACNIC | 670 100% |
| 2803:3c90::/32 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS273019: AS273019:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273019 isn't in the set, or no route object for AS273019 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS273019 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS273019:AS-CUSTOMERS | In no IRR database read today. | |||||
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 19 are in fix.csv.
- Route object: none18
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.12.168.0/23 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.172.0/24 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.174.0/24 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.168.0/24 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.169.0/24 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.170.0/24 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.171.0/24 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.173.0/24 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:207::/48 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:208::/48 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:a00::/39 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:c00::/39 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.170.0/23 | No route object for it. A route object for 190.12.168.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.172.0/23 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.174.0/23 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 190.12.175.0/24 | No route object for it. A route object for 190.12.172.0/22 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:a00::/40 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| Route object: none | 2803:3c90:c00::/40 | No route object for it. A route object for 2803:3c90::/32 with origin AS273019 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273019 in the RIR database for the space. |
| AS-SET: not found | AS273019:AS-CUSTOMERS | PeeringDB names AS273019:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS273019 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.