MPPS

BGP inherited
Cluster stats
Netblocks9 · 343 IPv4 addresses
All fragments 14 blocks across 5 clusters
Cluster ID208831183
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

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.108.53.0/24 MPPS RIPE ASSIGNED PA ● low
195.108.235.0/29 MPPS RIPE ASSIGNED PA ● low
195.108.235.8/29 MPPS RIPE ASSIGNED PA ● low
195.108.246.64/27 MPPS RIPE ASSIGNED PA ● low
195.108.247.128/28 MPPS RIPE ASSIGNED PA ● low
195.108.248.48/29 MPPS RIPE ASSIGNED PA ● low
195.108.248.56/29 MPPS RIPE ASSIGNED PA ● low
195.108.251.136/29 MPPS RIPE ASSIGNED PA ● low
212.136.227.192/29 MPPS RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE NLNET-MNT