Network · data from 2026-11-12

AS269940 CABLE SISTEMA

Registry name: AS269940 - CABLE SISTEMA S.R.L. DE C.V., HN · PeeringDB

4IPv4 routes 100.0% 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

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS269940, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269940, 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.83.119.0/24	Valid	Other IRR onlyRADB	671 100%	67
190.83.116.0/24	Valid	Other IRR onlyRADB	667 99%	67
190.83.117.0/24	Valid	Other IRR onlyRADB	667 99%	67
190.83.118.0/24	Valid	Other IRR onlyRADB	667 99%	67
2803:9ae0::/32	Valid	RIR databaseLACNIC	631 99%	67

AS-SET

PeeringDB's irr_as_set for AS269940: AS269940:AS-PEERING. 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 (AS269940 isn't in the set, or no route object for AS269940 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	Route objects	AS269940 in it	Not covered
AS269940:AS-PEERING	LACNIC	12	1	51	No	5

Name

Database

ASNs

Sets

Route objects

AS269940 in it

Not covered

AS269940:AS-PEERING

LACNIC

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

Route object: RIR4
AS-SET: own ASN1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	190.83.119.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	190.83.116.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	190.83.117.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	190.83.118.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
AS-SET: own ASN	AS269940:AS-PEERING	AS269940 isn't in AS269940:AS-PEERING (LACNIC) once expanded. Add AS269940 to it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

190.83.119.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

190.83.116.0/24

Route object only in RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

190.83.117.0/24

Route object only in RADB. Add it in the RIR database for the space.

667 of 673

Route object: RIR

190.83.118.0/24

Route object only in RADB. Add it in the RIR database for the space.

667 of 673

AS-SET: own ASN

AS269940:AS-PEERING

AS269940 isn't in AS269940:AS-PEERING (LACNIC) once expanded. Add AS269940 to it.

Route objects not announced

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


190.83.116.0/22	LACNIC	Valid

190.83.116.0/22

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.