MUENET

BGP inherited
Cluster stats
Netblocks5 · 65,535 IPv4 addresses
Registered in Germany (2) · Japan (1)
All fragments 11 blocks across 7 clusters
Cluster ID210266193
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.192.186/32 MUENET PEERINGDB ASSIGNED ● high
185.1.170.80/32 MUENET PEERINGDB ASSIGNED ● high
2001:7f8::3:101f:0:1/128 MUENET PEERINGDB ASSIGNED ● high
2001:7f8:9e:0:3:101f:0:1/128 MUENET PEERINGDB ASSIGNED ● high
160.28.0.0/16 MUENET APNIC ALLOCATED PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MUENET” — 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.
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: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (4 of 5)
No discrepancies found among checked blocks.

NIC Handles

AS200735 JM2485-AP JM2485-AP MAINT-JPNIC