bgpreport

Network · data from 2026-11-12

AS60300 365 Midlar

Registry name: Vodafone_Iceland Syn hf, IS · PeeringDB

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

Announced routes

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

193.4.167.0/24 Invalid: origin None 1 0%low visibility 1
194.144.208.0/23 Invalid: origin None 1 0%low visibility 1
194.144.218.0/23 Invalid: origin None 1 0%low visibility 1
194.144.241.0/24 Invalid: origin None 1 0%low visibility 1
194.144.250.0/23 Invalid: origin None 1 0%low visibility 1
194.144.252.0/23 Invalid: origin None 1 0%low visibility 1
194.144.255.0/24 Invalid: origin None 1 0%low visibility 1
213.176.128.0/24 Invalid: origin None 1 0%low visibility 1
213.176.143.0/24 Invalid: origin None 1 0%low visibility 1
193.4.184.0/21 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
193.4.216.0/21 Invalid: origin RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS60300'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 24 are in fix.csv.

  • ROA: origin11
  • Route object: none9
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin193.4.167.0/24ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none193.4.167.0/24No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.208.0/23ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.208.0/23No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.218.0/23ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.218.0/23No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.241.0/24ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.241.0/24No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.250.0/23ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.250.0/23No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.252.0/23ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.252.0/23No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin194.144.255.0/24ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none194.144.255.0/24No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin213.176.128.0/24ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none213.176.128.0/24No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin213.176.143.0/24ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
Route object: none213.176.143.0/24No route object for it. Add a route object with origin AS60300 in the RIR database for the space.1 of 673
ROA: origin193.4.184.0/21ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673
ROA: origin193.4.216.0/21ROAs covering it name AS12969, not AS60300. If AS60300 should announce it, add a ROA for AS60300.1 of 673

Route objects not announced

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

5.23.64.0/19RIPEInvalid: origin
46.227.114.96/27RIPEValid
185.21.16.0/22RIPEInvalid: origin
2a00:4d60::/32RIPENo 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.