bgpreport

Network · data from 2026-11-12

AS41073 Raidio Telefis Eireann

Registry name: RTE Raidio Teilifis Eireann, IE · PeeringDB

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

Announced routes

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

89.207.60.21/32 Invalid: maxLength Nonecovered by 89.207.56.0/21 1 0%low visibility 1
185.54.104.0/26 Invalid: maxLength Nonecovered by 185.54.104.0/22 1 0%low visibility 1
185.54.105.0/26 Invalid: maxLength Nonecovered by 185.54.104.0/22 1 0%low visibility 1
2a00:1ed9:104::/64 Invalid: maxLength Nonecovered by 2a00:1ed9::/32 1 0%low visibility 1
2a00:1ed9:105::/64 Invalid: maxLength Nonecovered by 2a00:1ed9::/32 1 0%low visibility 1
89.207.57.0/24 Valid Nonecovered by 89.207.56.0/21 1 0%low visibility 1
89.207.58.0/24 Valid Nonecovered by 89.207.56.0/21 1 0%low visibility 1
89.207.56.0/21 Valid RIR databaseRIPE 673 100% 67
185.54.104.0/22 Valid RIR databaseRIPE 673 100% 67
2a00:1ed8::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS41073: RIPE::AS41073:AS-RTE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS41073 isn't in the set, or no route object for AS41073 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS41073 in itNot covered
RIPE::AS41073:AS-RTE RIPE 115 Yes 5

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

  • ROA: maxLength5
  • Route object: none7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength89.207.60.21/32ROA 89.207.56.0/21 AS41073 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 89.207.60.21/32.1 of 673
Route object: none89.207.60.21/32No route object for it. A route object for 89.207.56.0/21 with origin AS41073 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41073 in the RIR database for the space.1 of 673
ROA: maxLength185.54.104.0/26ROA 185.54.104.0/22 AS41073 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 185.54.104.0/26.1 of 673
Route object: none185.54.104.0/26No route object for it. A route object for 185.54.104.0/22 with origin AS41073 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41073 in the RIR database for the space.1 of 673
ROA: maxLength185.54.105.0/26ROA 185.54.104.0/22 AS41073 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 185.54.105.0/26.1 of 673
Route object: none185.54.105.0/26No route object for it. A route object for 185.54.104.0/22 with origin AS41073 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41073 in the RIR database for the space.1 of 673
ROA: maxLength2a00:1ed9:104::/64ROA 2a00:1ed8::/29 AS41073 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:1ed9:104::/64.1 of 636
Route object: none2a00:1ed9:104::/64No route object for it. A route object for 2a00:1ed9::/32 with origin AS41073 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS41073 in the RIR database for the space.1 of 636
ROA: maxLength2a00:1ed9:105::/64ROA 2a00:1ed8::/29 AS41073 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:1ed9:105::/64.1 of 636
Route object: none2a00:1ed9:105::/64No route object for it. A route object for 2a00:1ed9::/32 with origin AS41073 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS41073 in the RIR database for the space.1 of 636
Route object: none89.207.57.0/24No route object for it. A route object for 89.207.56.0/21 with origin AS41073 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41073 in the RIR database for the space.1 of 673
Route object: none89.207.58.0/24No route object for it. A route object for 89.207.56.0/21 with origin AS41073 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41073 in the RIR database for the space.1 of 673

Route objects not announced

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

185.54.107.0/24RIPEValid
2a00:1ed9::/32RIPEValid

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.