bgpreport

Network · data from 2026-11-12

AS28378 TV Rey de Occidente

Registry name: AS28378 - TV Rey de Occidente, S.A. de C.V., MX · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28378, 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.
201.150.244.0/22 No ROA Other origin only 673 100% 67
201.150.248.0/22 No ROA Other origin only 673 100% 67
201.150.252.0/23 No ROA Other origin only 673 100% 67
138.122.252.0/22 Valid RIR databaseLACNIC 673 100% 67
168.227.68.0/24 Valid RIR databaseLACNIC 673 100% 67
168.227.69.0/24 Valid RIR databaseLACNIC 673 100% 67
168.227.70.0/24 Valid RIR databaseLACNIC 673 100% 67
168.227.71.0/24 Valid RIR databaseLACNIC 673 100% 67
201.150.224.0/21 Valid RIR databaseLACNIC 673 100% 67
201.150.232.0/23 Valid RIR databaseLACNIC 673 100% 67
201.150.234.0/23 Valid RIR databaseLACNIC 673 100% 67
201.150.236.0/23 Valid RIR databaseLACNIC 673 100% 67
201.150.238.0/23 Valid RIR databaseLACNIC 673 100% 67
201.150.240.0/22 Valid RIR databaseLACNIC 673 100% 67
201.150.254.0/24 Valid RIR databaseLACNIC 673 100% 67
201.150.255.0/24 Valid RIR databaseLACNIC 673 100% 67
201.158.112.0/22 Valid RIR databaseLACNIC 673 100% 67
201.158.116.0/23 Valid RIR databaseLACNIC 673 100% 67
201.158.118.0/23 Valid RIR databaseLACNIC 673 100% 67
201.159.32.0/23 Valid RIR databaseLACNIC 673 100% 67
201.159.34.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.35.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.36.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.37.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.38.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.39.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.40.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.41.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.42.0/24 Valid RIR databaseLACNIC 673 100% 67
201.159.43.0/24 Valid RIR databaseLACNIC 673 100% 67
200.23.78.0/23 Valid RIR databaseLACNIC 672 100% 67
200.23.80.0/23 Valid RIR databaseLACNIC 672 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none201.150.244.0/22No ROA covers it. Add a ROA for AS28378, maxLength 22.673 of 673
Route object: none201.150.244.0/22Route objects for it name AS8151. Add a route object with origin AS28378 in the RIR database for the space.673 of 673
ROA: none201.150.248.0/22No ROA covers it. Add a ROA for AS28378, maxLength 22.673 of 673
Route object: none201.150.248.0/22Route objects for it name AS8151. Add a route object with origin AS28378 in the RIR database for the space.673 of 673
ROA: none201.150.252.0/23No ROA covers it. Add a ROA for AS28378, maxLength 23.673 of 673
Route object: none201.150.252.0/23Route objects for it name AS8151. Add a route object with origin AS28378 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS28378 is announced.

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.