bgpreport

Network · data from 2026-11-12

AS57066 yle Yleisradio Oy

Registry name: yle Yleisradio Oy, FI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57066, 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.
2001:67c:2e30::/48 No ROA RIR databaseRIPE 634 100% 67
91.229.138.0/24 Valid Nonecovered by 91.229.138.0/23 673 100% 67
91.229.137.0/24 Valid RIR databaseRIPE 672 100% 67
91.229.138.0/23 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS57066 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:2e30::/48No ROA covers it. Add a ROA for AS57066, maxLength 48.634 of 636
Route object: none91.229.138.0/24No route object for it. A route object for 91.229.138.0/23 with origin AS57066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57066 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS57066 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.