Network · data from 2026-11-12

AS197974 Vladislav Nitsenko

Registry name: PLYM-AS Vladislav Nitsenko, EE · PeeringDB

5IPv4 routes 20.0% RPKI valid · 20.0% with a route object

0IPv6 routes

4RPKI invalid 4 origin · 0 maxLength

0No ROA 4 with no route object for this origin

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

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

Announced routes

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


94.118.152.0/24	Invalid: origin	Other origin only	6 1%low visibility	4
69.33.168.0/24	Invalid: origin	Other origin only	2 0%low visibility	1
104.234.159.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
104.234.203.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
64.205.55.0/24	Valid	RIR databaseARIN, RADB	670 100%	66

94.118.152.0/24

Invalid: origin

Other origin only

6 1%low visibility

69.33.168.0/24

Invalid: origin

Other origin only

2 0%low visibility

104.234.159.0/24

Invalid: origin

Other origin only

1 0%low visibility

104.234.203.0/24

Invalid: origin

Other origin only

1 0%low visibility

64.205.55.0/24

Valid

RIR databaseARIN, RADB

670 100%

AS-SET

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

ROA: origin4
Route object: none4

Change	Prefix or set	Detail	Full-table peers
ROA: origin	94.118.152.0/24	ROAs covering it name AS834, not AS197974. If AS197974 should announce it, add a ROA for AS197974.	6 of 673
Route object: none	94.118.152.0/24	Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.	6 of 673
ROA: origin	69.33.168.0/24	ROAs covering it name AS834, not AS197974. If AS197974 should announce it, add a ROA for AS197974.	2 of 673
Route object: none	69.33.168.0/24	Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.	2 of 673
ROA: origin	104.234.159.0/24	ROAs covering it name AS29802, not AS197974. If AS197974 should announce it, add a ROA for AS197974.	1 of 673
Route object: none	104.234.159.0/24	Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.	1 of 673
ROA: origin	104.234.203.0/24	ROAs covering it name AS403157, not AS197974. If AS197974 should announce it, add a ROA for AS197974.	1 of 673
Route object: none	104.234.203.0/24	Route objects for it name AS403157. Add a route object with origin AS197974 in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

94.118.152.0/24

ROAs covering it name AS834, not AS197974. If AS197974 should announce it, add a ROA for AS197974.

6 of 673

Route object: none

94.118.152.0/24

Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.

6 of 673

ROA: origin

69.33.168.0/24

ROAs covering it name AS834, not AS197974. If AS197974 should announce it, add a ROA for AS197974.

2 of 673

Route object: none

69.33.168.0/24

Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.

2 of 673

ROA: origin

104.234.159.0/24

ROAs covering it name AS29802, not AS197974. If AS197974 should announce it, add a ROA for AS197974.

1 of 673

Route object: none

104.234.159.0/24

Route objects for it name AS834. Add a route object with origin AS197974 in the RIR database for the space.

1 of 673

ROA: origin

104.234.203.0/24

ROAs covering it name AS403157, not AS197974. If AS197974 should announce it, add a ROA for AS197974.

1 of 673

Route object: none

104.234.203.0/24

Route objects for it name AS403157. Add a route object with origin AS197974 in the RIR database for the space.

1 of 673

Route objects not announced

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