Miegl Net

MieglNet
Registry
Cluster stats
Netblocks6
All fragments 20 blocks across 15 clusters
Cluster ID206023518
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name 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-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.167.113/32 MieglNet PEERINGDB ASSIGNED ● high
193.189.83.209/32 MieglNet PEERINGDB ASSIGNED ● high
2001:7f8:33::a121:951:1/128 MieglNet PEERINGDB ASSIGNED ● high
2001:7f8:d0::3:3807:1/128 MieglNet PEERINGDB ASSIGNED ● high
2001:7f8:d0:4e4c:0:3:3807:1/128 MieglNet PEERINGDB ASSIGNED ● high
2001:7f8:f2:e1:0:21:951:1/128 MieglNet PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MieglNet” — 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.
Combined view of all 15 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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS210951