bgpreport

Network · data from 2026-11-12

AS202376 ARVID-LOGICUM Arvid Logicum OU

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

8IPv4 routes 37.5% RPKI valid · 100.0% with a route object
3IPv6 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
3Route objects not announced registered with origin AS202376, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202376, 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.209.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.5.210.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.5.211.0/24 No ROA Other IRR onlyRADB 673 100% 67
109.94.209.0/24 No ROA RIR databaseRIPE 673 100% 67
176.118.167.0/24 No ROA RIR databaseRIPE 673 100% 67
2.59.166.0/24 Valid RIR databaseRIPE 672 100% 67
2.59.167.0/24 Valid RIR databaseRIPE 672 100% 67
81.25.69.0/24 Valid RIR databaseRIPE 672 100% 67
2a09:f540::/32 Valid RIR databaseRIPE 636 100% 67
2a09:f540:3::/48 Valid RIR databaseRIPE 636 100% 67
2a09:f541::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: none5
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none149.5.209.0/24No ROA covers it. Add a ROA for AS202376, maxLength 24.673 of 673
Route object: RIR149.5.209.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.5.210.0/24No ROA covers it. Add a ROA for AS202376, maxLength 24.673 of 673
Route object: RIR149.5.210.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.5.211.0/24No ROA covers it. Add a ROA for AS202376, maxLength 24.673 of 673
Route object: RIR149.5.211.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none109.94.209.0/24No ROA covers it. Add a ROA for AS202376, maxLength 24.673 of 673
ROA: none176.118.167.0/24No ROA covers it. Add a ROA for AS202376, maxLength 24.673 of 673

Route objects not announced

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

2.59.166.0/23RIPENo ROA
149.5.210.0/23RADBNo ROA
2a09:f540:2::/48RIPEValid

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.