LEGIONCOM LTD

BGP inherited

Cluster stats

Netblocks	9 · 4,864 IPv4 addresses
All fragments	10 blocks across 2 clusters
Cluster ID	209240692
Registry	BGP
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

5 weekly snapshots · JSON

9 0 netblocks since 2026-07-05

2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
91.204.164.0/22	LEGIONCOM LTD	BGP	ANNOUNCED	● high
91.204.164.0/22	LEGIONCOM LTD	RIPE	ASSIGNED PI	● high
91.222.228.0/22	LEGIONCOM LTD	RIPE	ASSIGNED PI	● high
91.222.228.0/22	LEGIONCOM LTD	BGP	ANNOUNCED	● high
91.222.231.0/24	LEGIONCOM LTD	BGP	ANNOUNCED	● high
195.138.206.0/24	LEGIONCOM LTD	RIPE	ASSIGNED PI	● high
195.138.206.0/24	LEGIONCOM LTD	BGP	ANNOUNCED	● high
2001:67c:16c::/48	LEGIONCOM LTD	RIPE	ASSIGNED PI	● high
185.86.135.0/29	legioncom-net	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

legioncom_Moscow 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.

Moscow via PJSC Rostelecom sub-allocation

Network trust

what's this?

RPKI hygiene: F how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

AS41554 DUMY-RIPE DUMY-RIPE LEGIONCOM-MNT LEGIONCOM-MNT ORG-JL12-RIPE RIPE-NCC-END-MNT ROSNIIROS-MNT ULCM-MNT