bgpreport

Network · data from 2026-11-12

AS269729 GRUPO MULTICABLES DE CORTES

Registry name: AS269729 - GRUPO MULTICABLES DE CORTES S.R.L de C.V, HN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269729, 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:9160::/48 No ROA None 636 100% 67
45.181.85.0/24 Valid Nonecovered by 45.181.84.0/22 664 99% 67
45.181.84.0/24 Valid Nonecovered by 45.181.84.0/22 663 99% 67
45.181.87.0/24 Valid Nonecovered by 45.181.84.0/22 663 99% 67
45.181.86.0/24 Valid Nonecovered by 45.181.84.0/22 661 98% 67
46.29.30.0/24 Valid RIR databaseRIPE 662 98% 67

AS-SET

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

  • ROA: none1
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2803:9160::/48No ROA covers it. Add a ROA for AS269729, maxLength 48.636 of 636
Route object: none2803:9160::/48No route object for it. Add a route object with origin AS269729 in the RIR database for the space.636 of 636
Route object: none45.181.85.0/24No route object for it. A route object for 45.181.84.0/22 with origin AS269729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269729 in the RIR database for the space.664 of 673
Route object: none45.181.84.0/24No route object for it. A route object for 45.181.84.0/22 with origin AS269729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269729 in the RIR database for the space.663 of 673
Route object: none45.181.87.0/24No route object for it. A route object for 45.181.84.0/22 with origin AS269729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269729 in the RIR database for the space.663 of 673
Route object: none45.181.86.0/24No route object for it. A route object for 45.181.84.0/22 with origin AS269729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269729 in the RIR database for the space.661 of 673

Route objects not announced

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

45.181.84.0/22NTTCOM, RADBNo ROA

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.