Network · data from 2026-11-12

AS41943 vmi-kista Vaddo Media Information IS AB

Registry name: vmi-kista Vaddo Media Information IS AB, SE · not in PeeringDB

18IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS41943, seen from no peer

Announced routes

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


84.246.134.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.32.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.33.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.34.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.35.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.36.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.37.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.38.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.39.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.40.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.41.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.42.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.43.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.44.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.45.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.46.0/24	Valid	RIR databaseRIPE	671 100%	67
217.25.47.0/24	Valid	RIR databaseRIPE	671 100%	67
2a03:f600::/32	Valid	RIR databaseRIPE	636 100%	67
217.25.32.0/20	Valid	RIR databaseRIPE	2 0%low visibility	2

84.246.134.0/24

Valid

RIR databaseRIPE

671 100%

217.25.32.0/24

Valid

RIR databaseRIPE

671 100%

217.25.33.0/24

Valid

RIR databaseRIPE

671 100%

217.25.34.0/24

Valid

RIR databaseRIPE

671 100%

217.25.35.0/24

Valid

RIR databaseRIPE

671 100%

217.25.36.0/24

Valid

RIR databaseRIPE

671 100%

217.25.37.0/24

Valid

RIR databaseRIPE

671 100%

217.25.38.0/24

Valid

RIR databaseRIPE

671 100%

217.25.39.0/24

Valid

RIR databaseRIPE

671 100%

217.25.40.0/24

Valid

RIR databaseRIPE

671 100%

217.25.41.0/24

Valid

RIR databaseRIPE

671 100%

217.25.42.0/24

Valid

RIR databaseRIPE

671 100%

217.25.43.0/24

Valid

RIR databaseRIPE

671 100%

217.25.44.0/24

Valid

RIR databaseRIPE

671 100%

217.25.45.0/24

Valid

RIR databaseRIPE

671 100%

217.25.46.0/24

Valid

RIR databaseRIPE

671 100%

217.25.47.0/24

Valid

RIR databaseRIPE

671 100%

2a03:f600::/32

Valid

RIR databaseRIPE

636 100%

217.25.32.0/20

Valid

RIR databaseRIPE

2 0%low visibility

AS-SET

AS41943 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS41943 is announced.

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.