Komus LLC

BGP inherited

Cluster stats

Netblocks	6 · 838 IPv4 addresses
All fragments	11 blocks across 5 clusters
Cluster ID	208796990
Registry	BGP
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

5 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
91.220.1.0/24	Komus LLC	BGP	ANNOUNCED	● high
91.220.1.0/24	Komus LLC	RIPE	ASSIGNED PI	● high
195.209.182.0/24	Komus LLC	BGP	ANNOUNCED	● high
94.139.111.192/26	KOMUS-NET	RIPE	ASSIGNED PA	● low
212.48.49.48/30	Komus	RIPE	ASSIGNED PA	● low
213.85.225.200/29	Komus-net	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

Komus-ROSTOV-NET 2 blocks
Komus_-R2_Ryazan 1 blocks
KOMUS-TULA 1 blocks
KOMUS-NET-LEN 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.

FORTUNA-KOMUS-NET sub-allocation
INKOMUS-LTD via PJSC Rostelecom sub-allocation
CORBINA-KOMUS sub-allocation
Volgograd_TSZH_Komus1_LAN via JSC RDE "Unico" sub-allocation
KOMUSSPB-LAN via PJSC MegaFon sub-allocation
Sovintel Msk Komus sub-allocation
Komus_-R2_Ryazan via PJSC Rostelecom sub-allocation
Komus via JSC RDE "Unico" sub-allocation

NIC Handles

AS51613 COMSTAR-MNT DUMY-RIPE DUMY-RIPE KOMUS-MNT KOMUS-MNT ORG-KL385-RIPE RIPE-NCC-END-MNT ROSNIIROS-MNT TASCOM-MNT-RIPE cnt-mnt