AVTODOM

BGP inherited

Cluster stats

Netblocks	6 · 534 IPv4 addresses
Registered in	Russia (5) · KZ (1)
All fragments	9 blocks across 4 clusters
Cluster ID	209854478
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
37.151.43.40/30	AVTODOM	RIPE	ASSIGNED PA	● low
83.242.194.0/23	AVTODOM	RIPE	ASSIGNED PA	● low
89.175.178.176/29	AVTODOM	RIPE	ASSIGNED PA	● low
212.248.75.216/29	AVTODOM	RIPE	ASSIGNED PA	● low
213.85.2.212/30	avtodom-net	RIPE	ASSIGNED PA	● low
213.85.10.12/30	avtodom-net	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “AVTODOM” — 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.

AVTODOM-NET2 1 blocks
AVTODOM-MINSK 1 blocks
Avtodom-M 1 blocks

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.

AVTODOM-NET2 sub-allocation
CORBINA-AVTODOM sub-allocation
Beeline Msk Avtodom sub-allocation
Avtodom Bahturova12 via JSC RDE "Unico" sub-allocation
AVTODOM-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation

Network trust

what's this?

RPKI hygiene: D how networks compare →

33.3% of checked blocks have valid RPKI ROA coverage (2 of 6)

No discrepancies found among checked blocks.

NIC Handles

COMSTAR-MNT DUMY-RIPE DUMY-RIPE KNIC-MNT MTU-NOC cnt-mnt