Network · data from 2026-11-12

AS210006 ASKZ Shereverov Marat Ahmedovich

Registry name: ASKZ Shereverov Marat Ahmedovich, KZ · not in PeeringDB

4IPv4 routes 50.0% RPKI valid · 50.0% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


45.87.249.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
45.154.244.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
86.54.25.0/24	Valid	RIR databaseRIPE	664 99%	68
178.20.210.0/24	Valid	RIR databaseRIPE	661 98%	68

45.87.249.0/24

Invalid: origin

Other origin only

2 0%low visibility

45.154.244.0/24

Invalid: origin

Other origin only

2 0%low visibility

86.54.25.0/24

Valid

RIR databaseRIPE

664 99%

178.20.210.0/24

Valid

RIR databaseRIPE

661 98%

AS-SET

AS210006 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 4 are in fix.csv.

ROA: origin2
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	45.87.249.0/24	ROAs covering it name AS60781, not AS210006. If AS210006 should announce it, add a ROA for AS210006.	2 of 673
Route object: none	45.87.249.0/24	Route objects for it name AS60781. Add a route object with origin AS210006 in the RIR database for the space.	2 of 673
ROA: origin	45.154.244.0/24	ROAs covering it name AS60781, not AS210006. If AS210006 should announce it, add a ROA for AS210006.	2 of 673
Route object: none	45.154.244.0/24	Route objects for it name AS60781. Add a route object with origin AS210006 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

45.87.249.0/24

ROAs covering it name AS60781, not AS210006. If AS210006 should announce it, add a ROA for AS210006.

2 of 673

Route object: none

45.87.249.0/24

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

2 of 673

ROA: origin

45.154.244.0/24

ROAs covering it name AS60781, not AS210006. If AS210006 should announce it, add a ROA for AS210006.

2 of 673

Route object: none

45.154.244.0/24

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

2 of 673

Route objects not announced

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