bgpreport

Network · data from 2026-11-12

AS12969 Reykjavik Fibre Network

Registry name: Vodafone_Iceland Ljosleidarinn ehf, IS · PeeringDB

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

Announced routes

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

80.77.140.0/23 Invalid: origin None 1 0%low visibility 1
194.144.166.0/24 Invalid: maxLength Nonecovered by 194.144.0.0/16 1 0%low visibility 1
213.220.64.0/21 Invalid: maxLength Nonecovered by 213.220.64.0/18 1 0%low visibility 1
213.220.78.0/23 Invalid: maxLength Nonecovered by 213.220.64.0/18 1 0%low visibility 1
213.220.81.0/24 Invalid: maxLength Nonecovered by 213.220.64.0/18 1 0%low visibility 1
213.220.120.0/21 Invalid: maxLength Nonecovered by 213.220.64.0/18 1 0%low visibility 1
185.24.0.0/24 Invalid: maxLength RIR databaseRIPE 1 0%low visibility 1
185.177.132.0/22 No ROA Other origin only 672 100% 67
2a00:4d60::/32 No ROA RIR databaseRIPE 636 100% 69
2a02:48::/32 No ROA RIR databaseRIPE 636 100% 69
5.23.64.0/20 Valid Nonecovered by 5.23.64.0/19 672 100% 67
5.23.80.0/20 Valid Nonecovered by 5.23.64.0/19 672 100% 67
185.21.16.0/23 Valid Nonecovered by 185.21.16.0/22 672 100% 67
185.21.18.0/23 Valid Nonecovered by 185.21.16.0/22 672 100% 67
185.24.0.0/23 Valid Nonecovered by 185.24.0.0/22 672 100% 67
213.176.131.0/24 Valid Nonecovered by 213.176.128.0/19 672 100% 67
5.23.64.0/19 Valid RIR databaseRIPE 672 100% 67
46.239.192.0/18 Valid RIR databaseRIPE 672 100% 67
46.239.192.0/19 Valid RIR databaseRIPE 672 100% 67
46.239.224.0/19 Valid RIR databaseRIPE 672 100% 67
62.145.128.0/19 Valid RIR databaseRIPE 672 100% 67
81.15.0.0/17 Valid RIR databaseRIPE 672 100% 67
88.149.0.0/17 Valid RIR databaseRIPE 672 100% 67
89.160.128.0/17 Valid RIR databaseRIPE 672 100% 67
185.21.16.0/22 Valid RIR databaseRIPE 672 100% 67
185.24.0.0/22 Valid RIR databaseRIPE 672 100% 67
193.4.0.0/19 Valid RIR databaseRIPE 672 100% 67
193.4.4.0/24 Valid RIR databaseRIPE 672 100% 67
193.4.5.0/24 Valid RIR databaseRIPE 672 100% 67
193.4.56.0/23 Valid RIR databaseRIPE 672 100% 67
193.4.60.0/22 Valid RIR databaseRIPE 672 100% 67
193.4.64.0/18 Valid RIR databaseRIPE 672 100% 67
193.4.128.0/17 Valid RIR databaseRIPE 672 100% 67
194.144.0.0/16 Valid RIR databaseRIPE 672 100% 67
213.176.128.0/19 Valid RIR databaseRIPE 672 100% 67
213.213.128.0/19 Valid RIR databaseRIPE 672 100% 67
213.220.64.0/18 Valid RIR databaseRIPE 672 100% 67
217.9.128.0/20 Valid RIR databaseRIPE 672 100% 67
217.151.160.0/19 Valid RIR databaseRIPE 672 100% 67
217.171.208.0/20 Valid RIR databaseRIPE 672 100% 67
193.4.6.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS12969: RIPE::AS12969:AS-VFIS. 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 (AS12969 isn't in the set, or no route object for AS12969 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 objectsAS12969 in itNot covered
RIPE::AS12969:AS-VFIS RIPE 457435 Yes 2

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

  • ROA: origin1
  • ROA: maxLength6
  • ROA: none3
  • Route object: none13
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: origin80.77.140.0/23ROAs covering it name AS20963, not AS12969. If AS12969 should announce it, add a ROA for AS12969.1 of 673
Route object: none80.77.140.0/23No route object for it. Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength194.144.166.0/24ROA 194.144.0.0/16 AS12969 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 194.144.166.0/24.1 of 673
Route object: none194.144.166.0/24No route object for it. A route object for 194.144.0.0/16 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength213.220.64.0/21ROA 213.220.64.0/18 AS12969 has maxLength 18; the route is a /21. Raise the maxLength, or add a ROA for 213.220.64.0/21.1 of 673
Route object: none213.220.64.0/21No route object for it. A route object for 213.220.64.0/18 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength213.220.78.0/23ROA 213.220.64.0/18 AS12969 has maxLength 18; the route is a /23. Raise the maxLength, or add a ROA for 213.220.78.0/23.1 of 673
Route object: none213.220.78.0/23No route object for it. A route object for 213.220.64.0/18 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength213.220.81.0/24ROA 213.220.64.0/18 AS12969 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 213.220.81.0/24.1 of 673
Route object: none213.220.81.0/24No route object for it. A route object for 213.220.64.0/18 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength213.220.120.0/21ROA 213.220.64.0/18 AS12969 has maxLength 18; the route is a /21. Raise the maxLength, or add a ROA for 213.220.120.0/21.1 of 673
Route object: none213.220.120.0/21No route object for it. A route object for 213.220.64.0/18 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.1 of 673
ROA: maxLength185.24.0.0/24ROA 185.24.0.0/22 AS12969 has maxLength 22; ROA 185.24.0.0/23 AS12969 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 185.24.0.0/24.1 of 673
ROA: none185.177.132.0/22No ROA covers it. Add a ROA for AS12969, maxLength 22.672 of 673
Route object: none185.177.132.0/22Route objects for it name AS206743. Add a route object with origin AS12969 in the RIR database for the space.672 of 673
ROA: none2a00:4d60::/32No ROA covers it. Add a ROA for AS12969, maxLength 32.636 of 636
ROA: none2a02:48::/32No ROA covers it. Add a ROA for AS12969, maxLength 32.636 of 636
Route object: none5.23.64.0/20No route object for it. A route object for 5.23.64.0/19 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673
Route object: none5.23.80.0/20No route object for it. A route object for 5.23.64.0/19 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673
Route object: none185.21.16.0/23No route object for it. A route object for 185.21.16.0/22 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673
Route object: none185.21.18.0/23No route object for it. A route object for 185.21.16.0/22 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673
Route object: none185.24.0.0/23No route object for it. A route object for 185.24.0.0/22 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673
Route object: none213.176.131.0/24No route object for it. A route object for 213.176.128.0/19 with origin AS12969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12969 in the RIR database for the space.672 of 673

Route objects not announced

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

89.160.128.0/19RIPEInvalid: maxLength
89.160.160.0/19RIPEInvalid: maxLength
89.160.192.0/19RIPEInvalid: maxLength
89.160.224.0/19RIPEInvalid: maxLength
185.24.1.0/24RIPEInvalid: maxLength
185.24.2.0/24RIPEInvalid: maxLength
185.24.3.0/24RIPEInvalid: maxLength
193.4.7.0/24RIPEInvalid: maxLength
193.4.32.0/20RIPENo ROA
193.4.48.0/21RIPEValid
193.4.108.0/24RIPEInvalid: maxLength

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.