MEGGLE Group GmbH

MEGGLE-NET

GLEIF verified

LEI

5299009WLGROB3HKM878

Registered name

MEGGLE Group GmbH

Jurisdiction

Ultimate parent

No parent on file in GLEIF

Cluster stats

Netblocks	3
All fragments	10 blocks across 6 clusters
Cluster ID	204780062
Registry	RIPE
Owner jurisdiction	DE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	GLEIF legal-entity match
Legal identity	LEI 5299009WLGROB3HKM878
Shared handles	clustered on 5 shared RIR contact/maintainer handles
Registry names	3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (3)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
89.216.33.136/29	MEGGLE-NET	RIPE	ASSIGNED PA	● low
194.228.37.192/29	MEGGLE	RIPE	ASSIGNED PA	● low
195.29.217.156/30	Meggle	RIPE	ASSIGNED PA	● low

Corporate group (2 confirmed entities)

Meggle-Intertrade-GmbH 1 blocks

Possibly related to this organisation

what's this?

Same name family

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

MEGGLE-CZ 3 blocks
MEGGLE-BH 1 blocks
MEGGLE-HR 1 blocks
MEGGLE_SERBIA-NET 1 blocks

Combined view of all 6 name-family clusters →

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.

MEGGLE-BH via JP HT d.d. Mostar sub-allocation
Meggle-Intertrade-GmbH via T-Mobile Austria GmbH sub-allocation
MEGGLE-HR via Hrvatski Telekom d.d. sub-allocation
MEGGLE_SERBIA-NET via TELEKOM SRBIJA a.d. sub-allocation
CYS-MEGGLE via SpaceNet AG sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

AS5610-MTN DUMY-RIPE DUMY-RIPE HPT-MNT SBB-MNT