bgpreport

Network · data from 2026-11-12

AS28517 AS28517 - TV Azteca, S.A.B. de C.V.

Registry name: AS28517 - TV Azteca, S.A.B. de C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28517, 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.

200.38.96.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 672 100% 67
200.38.106.0/24 No ROA Nonecovered by 200.38.96.0/19 672 100% 67
200.38.120.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 672 100% 67
200.38.103.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.105.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.107.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.110.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.116.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.119.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.124.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 670 100% 67
200.38.127.0/24 No ROA Other origin onlycovered by 200.38.96.0/19 664 99% 67
200.38.101.0/24 No ROA Other IRR onlyRADB 672 100% 67
200.38.97.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.38.109.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.38.113.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.38.115.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.38.122.0/24 No ROA Other IRR onlyRADB 670 100% 67
200.38.123.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS28517 isn't in PeeringDB, where networks name their 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 43 are in fix.csv.

  • ROA: none18
  • Route object: none11
  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none200.38.96.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.672 of 673
Route object: none200.38.96.0/24Route objects for it name AS594, AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.672 of 673
ROA: none200.38.106.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.672 of 673
Route object: none200.38.106.0/24No route object for it. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.672 of 673
ROA: none200.38.120.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.672 of 673
Route object: none200.38.120.0/24Route objects for it name AS594, AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.672 of 673
ROA: none200.38.103.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.103.0/24Route objects for it name AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.105.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.105.0/24Route objects for it name AS594, AS8151, AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.107.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.107.0/24Route objects for it name AS198949. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.110.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.110.0/24Route objects for it name AS17072. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.116.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.116.0/24Route objects for it name AS594, AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.119.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.119.0/24Route objects for it name AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.124.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: none200.38.124.0/24Route objects for it name AS17072, AS32098. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.670 of 673
ROA: none200.38.127.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.664 of 673
Route object: none200.38.127.0/24Route objects for it name AS594, AS8151, AS17072. A route object for 200.38.96.0/19 with origin AS28517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28517 in the RIR database for the space.664 of 673
ROA: none200.38.101.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.672 of 673
Route object: RIR200.38.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.38.97.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.97.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.38.109.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.109.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.38.113.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.113.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.38.115.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.115.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.38.122.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.122.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.38.123.0/24No ROA covers it. Add a ROA for AS28517, maxLength 24.670 of 673
Route object: RIR200.38.123.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

200.38.96.0/19RADBNo ROA
200.38.100.0/24RADBNo ROA
200.38.104.0/24RADBNo ROA
200.38.108.0/24RADBNo ROA
200.38.112.0/24RADBNo ROA
200.38.117.0/24RADBNo ROA
200.56.208.0/20RADBNo 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.