Network · data from 2026-11-12

AS51380 GREY-AS FOP Kovalchuk Igor Vasilevich

Registry name: GREY-AS FOP Kovalchuk Igor Vasilevich, UA · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

5Route objects not announced registered with origin AS51380, seen from no peer

Announced routes

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


91.218.192.0/24	Valid	RIR databaseRIPE	671 100%	68
91.218.193.0/24	Valid	RIR databaseRIPE	671 100%	68
195.20.4.0/23	Valid	RIR databaseRIPE	671 100%	68
195.20.5.0/24	Valid	RIR databaseRIPE	671 100%	68
195.20.6.0/24	Valid	RIR databaseRIPE	671 100%	68

AS-SET

AS51380 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 5 are in fix.csv.

Route object: not announced5

Route objects not announced

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


91.218.192.0/23	RIPE	Valid
95.84.73.0/24	RIPE	Invalid: origin
195.20.4.0/22	RIPE	No ROA
195.20.4.0/24	RIPE	Valid
195.20.7.0/24	RIPE	Valid

91.218.192.0/23

RIPE

Valid

95.84.73.0/24

RIPE

Invalid: origin

195.20.4.0/22

RIPE

No ROA

195.20.4.0/24

RIPE

Valid

195.20.7.0/24

RIPE

Valid

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.