MFR
Unresolved
Cluster stats
Netblocks9
All fragments 42 blocks across 25 clusters
Cluster ID191809615
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
43.254.82.247/32 MFR PEERINGDB ASSIGNED ● high
49.213.56.91/32 MFR PEERINGDB ASSIGNED ● high
103.80.212.17/32 MFR PEERINGDB ASSIGNED ● high
119.11.186.230/32 MFR PEERINGDB ASSIGNED ● high
2001:df4:10c0:8888:a:2120:1:1/128 MFR PEERINGDB ASSIGNED ● high
2001:df5:7880:0:3:3c21:0:1/128 MFR PEERINGDB ASSIGNED ● high
2401:91e0:31::212:1:1/128 MFR PEERINGDB ASSIGNED ● high
2404:c8:0:a:0:21:2001:1/128 MFR PEERINGDB ASSIGNED ● high
193.10.43.0/24 SE-MFR RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
44.4% of checked blocks have valid RPKI ROA coverage (4 of 9)
Possible discrepancies (1)

These blocks are registered to MFR but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

193.10.43.0/24 /24 authorized for AS1653 — Vetenskapsradet / SUNET

NIC Handles

AS212001 DUMY-RIPE DUMY-RIPE SUNET-MNT