Network · data from 2026-11-12

AS209153 ARVID Arvid Logicum OU

Registry name: ARVID Arvid Logicum OU, EE · not in PeeringDB

9IPv4 routes 44.4% 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

5No ROA 0 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209153, 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.5.212.0/24	No ROA	Other IRR onlyRADB	673 100%	67
149.5.215.0/24	No ROA	Other IRR onlyRADB	673 100%	67
154.59.224.0/24	No ROA	Other IRR onlyRADB	673 100%	67
154.59.226.0/24	No ROA	RIR databaseARIN	673 100%	67
154.59.227.0/24	No ROA	RIR databaseARIN	673 100%	67
2.59.164.0/23	Valid	RIR databaseRIPE	673 100%	67
93.183.100.0/24	Valid	RIR databaseRIPE	673 100%	67
2.59.164.0/24	Valid	RIR databaseRIPE	672 100%	67
2.59.165.0/24	Valid	RIR databaseRIPE	672 100%	67
2a09:f542::/32	Valid	RIR databaseRIPE	634 100%	67

AS-SET

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

ROA: none5
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: none	149.5.212.0/24	No ROA covers it. Add a ROA for AS209153, maxLength 24.	673 of 673
Route object: RIR	149.5.212.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	149.5.215.0/24	No ROA covers it. Add a ROA for AS209153, maxLength 24.	673 of 673
Route object: RIR	149.5.215.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	154.59.224.0/24	No ROA covers it. Add a ROA for AS209153, maxLength 24.	673 of 673
Route object: RIR	154.59.224.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	154.59.226.0/24	No ROA covers it. Add a ROA for AS209153, maxLength 24.	673 of 673
ROA: none	154.59.227.0/24	No ROA covers it. Add a ROA for AS209153, maxLength 24.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

149.5.212.0/24

No ROA covers it. Add a ROA for AS209153, maxLength 24.

673 of 673

Route object: RIR

149.5.212.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

149.5.215.0/24

No ROA covers it. Add a ROA for AS209153, maxLength 24.

673 of 673

Route object: RIR

149.5.215.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

154.59.224.0/24

No ROA covers it. Add a ROA for AS209153, maxLength 24.

673 of 673

Route object: RIR

154.59.224.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

154.59.226.0/24

No ROA covers it. Add a ROA for AS209153, maxLength 24.

673 of 673

ROA: none

154.59.227.0/24

No ROA covers it. Add a ROA for AS209153, maxLength 24.

673 of 673

Route objects not announced

Every route object with origin AS209153 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.