bgpreport

Network · data from 2026-11-12

AS8518 Radio Free Europe

Registry name: RFERL RFE/RL, INC., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8518, 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.
149.7.244.0/22 No ROA None 2 0%low visibility 2
149.7.244.0/24 No ROA None 2 0%low visibility 2
149.7.245.0/24 No ROA None 2 0%low visibility 2
149.7.246.0/24 No ROA None 2 0%low visibility 2
149.7.247.0/24 No ROA None 2 0%low visibility 2
193.111.128.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.129.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.130.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.131.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.132.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.133.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.134.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
193.111.135.0/24 Valid Nonecovered by 193.111.128.0/21 673 100% 67
91.102.96.0/21 Valid Other IRR onlyRADB 673 100% 66
94.198.112.0/21 Valid RIR databaseRADB, RIPE 673 100% 66
94.198.112.0/24 Valid RIR databaseRIPE 673 100% 70
94.198.119.0/24 Valid RIR databaseRIPE 673 100% 66
185.45.56.0/22 Valid RIR databaseRADB, RIPE 673 100% 66
193.111.128.0/21 Valid RIR databaseRADB, RIPE 673 100% 66
91.102.96.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.98.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.99.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.100.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.101.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.102.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.102.103.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.198.113.0/24 Valid RIR databaseRIPE 672 100% 67
94.198.114.0/24 Valid RIR databaseRIPE 672 100% 67
94.198.115.0/24 Valid RIR databaseRIPE 672 100% 67
94.198.116.0/24 Valid RIR databaseRIPE 672 100% 67
94.198.117.0/24 Valid RIR databaseRIPE 672 100% 67
94.198.118.0/24 Valid RIR databaseRIPE 672 100% 67
185.45.56.0/24 Valid RIR databaseRIPE 672 100% 67
185.45.57.0/24 Valid RIR databaseRIPE 672 100% 67
185.45.58.0/24 Valid RIR databaseRIPE 672 100% 67
185.45.59.0/24 Valid RIR databaseRIPE 672 100% 67
2a01:538:2::/48 Valid RIR databaseRIPE 605 95% 67
91.102.97.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS8518: AS-RFERL. 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 (AS8518 isn't in the set, or no route object for AS8518 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 objectsAS8518 in itNot covered
AS-RFERL In no IRR database read today.

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

  • ROA: none5
  • Route object: none13
  • Route object: RIR1
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none149.7.244.0/22No ROA covers it. Add a ROA for AS8518, maxLength 22.2 of 673
Route object: none149.7.244.0/22No route object for it. Add a route object with origin AS8518 in the RIR database for the space.2 of 673
ROA: none149.7.244.0/24No ROA covers it. Add a ROA for AS8518, maxLength 24.2 of 673
Route object: none149.7.244.0/24No route object for it. Add a route object with origin AS8518 in the RIR database for the space.2 of 673
ROA: none149.7.245.0/24No ROA covers it. Add a ROA for AS8518, maxLength 24.2 of 673
Route object: none149.7.245.0/24No route object for it. Add a route object with origin AS8518 in the RIR database for the space.2 of 673
ROA: none149.7.246.0/24No ROA covers it. Add a ROA for AS8518, maxLength 24.2 of 673
Route object: none149.7.246.0/24No route object for it. Add a route object with origin AS8518 in the RIR database for the space.2 of 673
ROA: none149.7.247.0/24No ROA covers it. Add a ROA for AS8518, maxLength 24.2 of 673
Route object: none149.7.247.0/24No route object for it. Add a route object with origin AS8518 in the RIR database for the space.2 of 673
Route object: none193.111.128.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.129.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.130.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.131.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.132.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.133.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.134.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: none193.111.135.0/24No route object for it. A route object for 193.111.128.0/21 with origin AS8518 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8518 in the RIR database for the space.673 of 673
Route object: RIR91.102.96.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: not foundAS-RFERLPeeringDB names AS-RFERL; no IRR database read has it.

Route objects not announced

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

195.248.66.0/24RIPENo ROA
2a01:538::/32RIPENo ROA
2a01:538:1::/48RIPENo 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.