bgpreport

Network · data from 2026-11-12

AS273953 TV COLOMBIA DIGITAL

Registry name: AS273953 - TV COLOMBIA DIGITAL SAS, CO · PeeringDB

6IPv4 routes 83.3% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS273953, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273953, 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.
38.10.240.0/22 No ROA Other IRR onlyRADB 670 100% 66
131.72.138.0/24 Valid RIR databaseLACNIC 670 100% 66
187.102.194.0/24 Valid RIR databaseLACNIC, RADB 670 100% 66
38.199.65.0/24 Valid RIR databaseARIN, RADB 669 99% 66
38.199.66.0/24 Valid RIR databaseARIN, RADB 669 99% 66
38.199.67.0/24 Valid RIR databaseARIN, RADB 669 99% 66
2803:df50::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

AS273953's PeeringDB record names no 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 10 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none38.10.240.0/22No ROA covers it. Add a ROA for AS273953, maxLength 22.670 of 673
Route object: RIR38.10.240.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS273953 whose prefix no peer sees AS273953 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.10.240.0/23RADBNo ROA
38.10.240.0/24RADBNo ROA
38.10.241.0/24RADBNo ROA
38.10.242.0/23RADBNo ROA
38.10.242.0/24RADBNo ROA
38.10.243.0/24RADBNo ROA
187.102.194.0/23LACNIC, RADBValid
187.102.195.0/24LACNIC, RADBValid

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.