MR-N

BGP inherited
Cluster stats
Netblocks6
All fragments 8 blocks across 2 clusters
Cluster ID205214667
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.145.39.176/29 MR-N RIPE ASSIGNED PA ● low
86.188.235.184/29 MR-N RIPE ASSIGNED PA ● low
2a00:2381:c0ae::/56 MR-N RIPE ASSIGNED ● low
2a00:2381:c0ae::/48 MR-N RIPE AGGREGATED-BY-LIR ● low
2a00:2381:e663::/48 MR-N RIPE AGGREGATED-BY-LIR ● low
2a00:2381:e663::/56 MR-N RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MR N” — 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.

Network trust

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

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE