bgpreport

Network · data from 2026-11-12

AS265566 TELESISTEMAS PENINSULARES

Registry name: AS265566 - TELESISTEMAS PENINSULARES SA DE CV, MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265566, 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.
45.172.92.0/24 Valid Nonecovered by 45.172.92.0/22 672 100% 67
2806:316:2::/48 Valid Nonecovered by 2806:316::/32 634 100% 67
2806:316:1::/48 Valid Nonecovered by 2806:316::/32 633 100% 67
45.172.93.0/24 Valid Other IRR onlyRADB 673 100% 67
45.172.92.0/22 Valid RIR databaseLACNIC 99 15% 38

AS-SET

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

  • Route object: none3
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none45.172.92.0/24No route object for it. A route object for 45.172.92.0/22 with origin AS265566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265566 in the RIR database for the space.672 of 673
Route object: none2806:316:2::/48No route object for it. A route object for 2806:316::/32 with origin AS265566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265566 in the RIR database for the space.634 of 636
Route object: none2806:316:1::/48No route object for it. A route object for 2806:316::/32 with origin AS265566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265566 in the RIR database for the space.633 of 636
Route object: RIR45.172.93.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

45.172.94.0/24RADBValid
45.172.95.0/24RADBValid
148.207.187.0/24RADBNo ROA
148.207.188.0/24RADBNo ROA
148.207.189.0/24RADBNo ROA
148.207.190.0/24RADBNo ROA
2806:316::/32LACNICValid

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.