bgpreport

Network · data from 2026-11-12

AS203676 ARJOM-AS

Registry name: ARJOM-AS Arjom Arinenko, EE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203676, 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.
151.242.239.0/24 No ROA None 667 99% 67
94.249.200.0/24 Valid RIR databaseRIPE 672 100% 66
179.253.186.0/24 Valid RIR databaseRIPE 671 100% 66
94.183.252.0/24 Valid RIR databaseRIPE 669 99% 66
185.177.231.0/24 Valid RIR databaseRIPE 669 99% 66

AS-SET

AS203676'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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none151.242.239.0/24No ROA covers it. Add a ROA for AS203676, maxLength 24.667 of 673
Route object: none151.242.239.0/24No route object for it. Add a route object with origin AS203676 in the RIR database for the space.667 of 673

Route objects not announced

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