bgpreport

Network · data from 2026-11-12

AS34686 AFFV-AS Affarsverken Karlskrona AB

Registry name: AFFV-AS Affarsverken Karlskrona AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34686, 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.78.216.0/21 No ROA Nonecovered by 80.78.208.0/20 673 100% 67
80.78.210.0/23 No ROA Nonecovered by 80.78.208.0/20 671 100% 67
80.78.212.0/22 No ROA Nonecovered by 80.78.208.0/20 671 100% 67
80.78.209.0/24 No ROA Nonecovered by 80.78.208.0/20 670 100% 67
80.78.208.0/20 No ROA RIR databaseRIPE 672 100% 67
2a00:a140::/32 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none80.78.216.0/21No ROA covers it. Add a ROA for AS34686, maxLength 21.673 of 673
Route object: none80.78.216.0/21No route object for it. A route object for 80.78.208.0/20 with origin AS34686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34686 in the RIR database for the space.673 of 673
ROA: none80.78.210.0/23No ROA covers it. Add a ROA for AS34686, maxLength 23.671 of 673
Route object: none80.78.210.0/23No route object for it. A route object for 80.78.208.0/20 with origin AS34686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34686 in the RIR database for the space.671 of 673
ROA: none80.78.212.0/22No ROA covers it. Add a ROA for AS34686, maxLength 22.671 of 673
Route object: none80.78.212.0/22No route object for it. A route object for 80.78.208.0/20 with origin AS34686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34686 in the RIR database for the space.671 of 673
ROA: none80.78.209.0/24No ROA covers it. Add a ROA for AS34686, maxLength 24.670 of 673
Route object: none80.78.209.0/24No route object for it. A route object for 80.78.208.0/20 with origin AS34686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34686 in the RIR database for the space.670 of 673
ROA: none80.78.208.0/20No ROA covers it. Add a ROA for AS34686, maxLength 20.672 of 673
ROA: none2a00:a140::/32No ROA covers it. Add a ROA for AS34686, maxLength 32.634 of 636

Route objects not announced

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

80.78.208.0/24RIPENo ROA
80.78.210.0/24RIPENo ROA
80.78.211.0/24RIPENo ROA
80.78.212.0/24RIPENo ROA
80.78.213.0/24RIPENo ROA
80.78.214.0/24RIPENo ROA
80.78.215.0/24RIPENo ROA
80.78.216.0/24RIPENo ROA
80.78.223.0/24RIPENo 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.