MTK-abonents-185-246-33

BGP inherited

Cluster stats

Netblocks	1
All fragments	4 blocks across 4 clusters
Cluster ID	205964095
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.246.33.0/24	MTK-abonents-185-246-33	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “MTK abonents 185 246” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

RIT-ABONENTS via Closed Joint Stock Company Radiotelephone sub-allocation
Nov11 via Nets and Services JCS sub-allocation
SIS-abonents-185-42-48 via Nets and Services JCS sub-allocation
SIS-abonents-185-42-50 via Nets and Services JCS sub-allocation
SIS-abonents-185-42-51 via Nets and Services JCS sub-allocation
MTK-abonents-185-246-32 via Moy Telecom LLC sub-allocation
MTK-abonents-185-246-34 via Moy Telecom LLC sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

RPKI-inferred operator Moy Telecom LLC

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

AR73192-RIPE DUMY-RIPE DUMY-RIPE ru-setii-1-mnt