bgpreport

Network · data from 2026-11-12

AS61490 Cable Norte TV

Registry name: AS61490 - Cable Norte Tv SA, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61490, 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:2380:1000::/36 Invalid: maxLength Nonecovered by 2803:2380::/32 1 0%low visibility 2
2803:2380:2000::/36 Invalid: maxLength Nonecovered by 2803:2380::/32 1 0%low visibility 2
131.108.140.0/24 Valid RIR databaseLACNIC 671 100% 67
131.108.142.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
131.108.141.0/24 Valid RIR databaseLACNIC, RADB 670 100% 66
131.108.143.0/24 Valid RIR databaseLACNIC, RADB 670 100% 66
2803:2380::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS61490: AS61490. 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 (AS61490 isn't in the set, or no route object for AS61490 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.

NameDatabaseASNsSets Route objectsAS61490 in itNot covered
AS61490 A single AS number, not a set: AS61490 (this network), 6 route objects.

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 5 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2803:2380:1000::/36ROA 2803:2380::/32 AS61490 has maxLength 32; the route is a /36. Raise the maxLength, or add a ROA for 2803:2380:1000::/36.1 of 636
Route object: none2803:2380:1000::/36No route object for it. A route object for 2803:2380::/32 with origin AS61490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61490 in the RIR database for the space.1 of 636
ROA: maxLength2803:2380:2000::/36ROA 2803:2380::/32 AS61490 has maxLength 32; the route is a /36. Raise the maxLength, or add a ROA for 2803:2380:2000::/36.1 of 636
Route object: none2803:2380:2000::/36No route object for it. A route object for 2803:2380::/32 with origin AS61490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61490 in the RIR database for the space.1 of 636

Route objects not announced

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

131.108.140.0/22LACNIC, 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.