bgpreport

Network · data from 2026-11-12

AS55408 Univision

Registry name: Univision-AS-AP - Univision LLC. To TTK STM1 UPSTREAM PROVIDER, MN · PeeringDB

3IPv4 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
17Route objects not announced registered with origin AS55408, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55408, 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.
122.201.21.0/24 Valid RIR databaseAPNIC 670 100% 67
122.201.22.0/24 Valid RIR databaseAPNIC 670 100% 67
192.82.78.0/24 Valid RIR databaseAPNIC 670 100% 67
2401:ffe0::/32 Valid RIR databaseAPNIC 635 100% 67

AS-SET

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

  • Route object: not announced17

Route objects not announced

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

202.70.32.0/20RADBNo ROA
202.70.32.0/21RADBNo ROA
202.70.32.0/22RADBNo ROA
202.70.32.0/23RADBNo ROA
202.70.34.0/23RADBNo ROA
202.70.36.0/22RADBNo ROA
202.70.36.0/23RADBNo ROA
202.70.38.0/23RADBNo ROA
202.70.39.0/24APNIC, NTTCOM, RADBValid
202.70.40.0/21RADBNo ROA
202.70.40.0/22RADBNo ROA
202.70.40.0/23RADBNo ROA
202.70.42.0/23RADBNo ROA
202.70.44.0/22RADBNo ROA
202.70.44.0/23RADBNo ROA
202.70.46.0/23RADBNo ROA
202.70.46.0/24APNIC, NTTCOM, RADBValid

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.