Network · data from 2026-11-12

AS204909 ZIN-AS Zimnitskaya Irina Nikolaevna

Registry name: ZIN-AS Zimnitskaya Irina Nikolaevna, RU · not in PeeringDB

0IPv4 routes

8IPv6 routes 62.5% RPKI valid · 62.5% with a route object

1RPKI invalid 1 origin · 0 maxLength

2No ROA 3 with no route object for this origin

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

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

Announced routes

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


2a11:7d01::/32	Invalid: origin	Other origin only	1 0%low visibility	1
2a11:77c1::/32	No ROA	None	2 0%low visibility	3
2a12:8785::/32	No ROA	None	2 0%low visibility	2
2a11:7d00::/32	Valid	RIR databaseRIPE	635 100%	69
2a11:ab83::/32	Valid	RIR databaseRIPE	635 100%	69
2a11:e2c5::/32	Valid	RIR databaseRIPE	634 100%	67
2a11:eac7::/32	Valid	RIR databaseRIPE	634 100%	69
2a12:f980::/32	Valid	RIR databaseRIPE	634 100%	69

2a11:7d01::/32

Invalid: origin

Other origin only

1 0%low visibility

2a11:77c1::/32

No ROA

None

2 0%low visibility

2a12:8785::/32

No ROA

None

2 0%low visibility

2a11:7d00::/32

Valid

RIR databaseRIPE

635 100%

2a11:ab83::/32

Valid

RIR databaseRIPE

635 100%

2a11:e2c5::/32

Valid

RIR databaseRIPE

634 100%

2a11:eac7::/32

Valid

RIR databaseRIPE

634 100%

2a12:f980::/32

Valid

RIR databaseRIPE

634 100%

AS-SET

AS204909 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 6 are in fix.csv.

ROA: origin1
ROA: none2
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2a11:7d01::/32	ROAs covering it name AS48108, not AS204909. If AS204909 should announce it, add a ROA for AS204909.	1 of 636
Route object: none	2a11:7d01::/32	Route objects for it name AS48108. Add a route object with origin AS204909 in the RIR database for the space.	1 of 636
ROA: none	2a11:77c1::/32	No ROA covers it. Add a ROA for AS204909, maxLength 32.	2 of 636
Route object: none	2a11:77c1::/32	No route object for it. Add a route object with origin AS204909 in the RIR database for the space.	2 of 636
ROA: none	2a12:8785::/32	No ROA covers it. Add a ROA for AS204909, maxLength 32.	2 of 636
Route object: none	2a12:8785::/32	No route object for it. Add a route object with origin AS204909 in the RIR database for the space.	2 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2a11:7d01::/32

ROAs covering it name AS48108, not AS204909. If AS204909 should announce it, add a ROA for AS204909.

1 of 636

Route object: none

2a11:7d01::/32

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

1 of 636

ROA: none

2a11:77c1::/32

No ROA covers it. Add a ROA for AS204909, maxLength 32.

2 of 636

Route object: none

2a11:77c1::/32

No route object for it. Add a route object with origin AS204909 in the RIR database for the space.

2 of 636

ROA: none

2a12:8785::/32

No ROA covers it. Add a ROA for AS204909, maxLength 32.

2 of 636

Route object: none

2a12:8785::/32

No route object for it. Add a route object with origin AS204909 in the RIR database for the space.

2 of 636

Route objects not announced

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