Network · data from 2026-11-12
AS269822 Colombia Mas Tv
Registry name: AS269822 - COLOMBIA MAS TV S.A.S, CO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269822, 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:15c0:4000::/36 | Invalid: maxLength | Nonecovered by 2803:15c0:4000::/34 | 65 10% |
| 190.60.63.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 45.65.232.0/22 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 103.219.234.0/23 | Valid | RIR databaseLACNIC, RADB | 673 100% |
| 185.91.192.0/23 | Valid | RIR databaseLACNIC | 673 100% |
| 185.91.192.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 185.91.193.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 190.102.120.0/23 | Valid | RIR databaseLACNIC | 673 100% |
| 103.212.83.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 103.219.234.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 185.104.165.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.102.120.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 190.102.121.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 190.102.122.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.65.232.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 45.65.233.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 45.65.234.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 45.65.235.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 103.219.235.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 185.104.166.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 185.104.167.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 190.102.123.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 223.27.115.0/24 | Valid | RIR databaseLACNIC, RADB | 670 100% |
| 190.102.126.0/24 | Valid | RIR databaseLACNIC, RADB | 664 99% |
| 2801:13:b800::/48 | Valid | RIR databaseLACNIC | 634 100% |
| 2803:15c0::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:15c0::/34 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:15c0:4000::/34 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:15c0:8000::/34 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:15c0:c000::/34 | Valid | RIR databaseLACNIC, RADB | 633 100% |
| 185.104.166.0/23 | Valid | RIR databaseLACNIC | 31 5%low visibility |
| 185.104.164.0/24 | Valid | RIR databaseLACNIC | 6 1%low visibility |
| 185.91.194.0/24 | Valid | RIR databaseLACNIC | 5 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS269822: AS269822:AS-COLOMBIAMAS. 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 (AS269822 isn't in the set, or no route object for AS269822 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 | AS269822 in it | Not covered |
|---|---|---|---|---|---|
| AS269822:AS-COLOMBIAMAS | LACNIC | 1 | 1 | Yes | 0 |
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.
- ROA: maxLength1
- Route object: none1
- Route object: RIR1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2803:15c0:4000::/36 | ROA 2803:15c0:4000::/34 AS269822 has maxLength 34; ROA 2803:15c0::/32 AS269822 has maxLength 32; the route is a /36. Raise the maxLength, or add a ROA for 2803:15c0:4000::/36. |
| Route object: none | 2803:15c0:4000::/36 | No route object for it. A route object for 2803:15c0:4000::/34 with origin AS269822 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269822 in the RIR database for the space. |
| Route object: RIR | 190.60.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269822 whose prefix no peer sees AS269822 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.91.192.0/22 | LACNIC, RADB | Valid |
| 185.91.195.0/24 | LACNIC | Valid |
| 185.104.164.0/22 | LACNIC, RADB | Valid |
| 190.102.120.0/21 | RADB | No ROA |
| 190.102.120.0/22 | LACNIC, RADB | Valid |
| 190.102.124.0/22 | RADB | No ROA |
| 190.102.124.0/23 | LACNIC | Valid |
| 190.102.124.0/24 | LACNIC, RADB | Valid |
| 190.102.125.0/24 | LACNIC, RADB | Valid |
| 190.102.127.0/24 | LACNIC, RADB | Valid |
| 2801:18:1800::/48 | LACNIC | Valid |
| 2803:3250:e061::/48 | 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.