Network · data from 2026-11-12

AS198138 Muskafidi Konstantin Nikolaevich

Registry name: tanaka-as Muskafidi Konstantin Nikolaevich, KZ · PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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

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

Announced routes

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


109.122.9.0/24	Valid	RIR databaseRIPE	672 100%	66
191.217.230.0/24	Valid	RIR databaseRIPE	672 100%	66
212.113.97.0/24	Valid	RIR databaseRIPE	672 100%	66
213.21.245.0/24	Valid	RIR databaseRIPE	672 100%	66
91.196.160.0/24	Valid	RIR databaseRIPE	670 100%	67
91.210.144.0/24	Valid	RIR databaseRIPE	670 100%	67
109.122.22.0/24	Valid	RIR databaseRIPE	669 99%	66
2a01:ecc0:b::/48	Valid	RIR databaseRIPE	634 100%	68
2a10:ab80:460::/48	Valid	RIR databaseRIPE	634 100%	68
2a0d:d940:1b::/48	Valid	RIR databaseRIPE	633 100%	67

AS-SET

AS198138's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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