Network · data from 2026-11-12
AS263245 CINECABLE TV
Registry name: AS263245 - CINECABLE TV, EC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263245, 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.107.232.0/24 | Valid | Nonecovered by 190.107.232.0/21 | 671 100% |
| 190.107.235.0/24 | Valid | Nonecovered by 190.107.232.0/21 | 669 99% |
| 190.107.234.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.107.236.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.107.237.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.107.233.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 190.107.238.0/24 | Valid | Other IRR onlyRADB | 666 99% |
AS-SET
PeeringDB's irr_as_set for AS263245: LACNIC::AS-CINECABLE-263245. 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 (AS263245 isn't in the set, or no route object for AS263245 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 | AS263245 in it | Not covered | |
|---|---|---|---|---|---|---|
| LACNIC::AS-CINECABLE-263245 | 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 11 are in fix.csv.
- Route object: none2
- Route object: RIR5
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.107.232.0/24 | No route object for it. A route object for 190.107.232.0/21 with origin AS263245 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263245 in the RIR database for the space. |
| Route object: none | 190.107.235.0/24 | No route object for it. A route object for 190.107.232.0/21 with origin AS263245 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263245 in the RIR database for the space. |
| Route object: RIR | 190.107.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.107.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.107.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.107.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.107.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | LACNIC::AS-CINECABLE-263245 | PeeringDB names LACNIC::AS-CINECABLE-263245; no IRR database read has it. |
Route objects not announced
Route objects with origin AS263245 whose prefix no peer sees AS263245 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.107.232.0/21 | RADB | Valid |
| 2803:d180::/32 | RADB | Valid |
| 2803:d180:ffff::/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.