MTU-Servers

BGP inherited
Cluster stats
Netblocks9 · 851 IPv4 addresses
Cluster ID208836877
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
62.5.255.0/26 MTU-Servers RIPE ASSIGNED PA ● low
62.5.255.64 – 62.5.255.91 MTU-Servers RIPE ASSIGNED PA ● low
62.118.91.0/24 MTU-Servers RIPE ASSIGNED PA ● low
195.7.179.224/27 MTU-Servers RIPE ASSIGNED PA ● low
195.34.32.0/24 MTU-Servers RIPE ASSIGNED PA ● low
195.34.34.224/27 MTU-Servers RIPE ASSIGNED PA ● low
195.34.35.64/26 MTU-Servers RIPE ASSIGNED PA ● low
195.42.79.128/26 MTU-Servers RIPE ASSIGNED PA ● low
195.42.80.192/26 MTU-Servers 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 (2)

These blocks are registered to MTU-Servers 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.

62.118.91.0/24 /24 authorized for AS8359 — MTS PJSC
195.34.32.0/24 /24 authorized for AS8359 — MTS PJSC

NIC Handles

DUMY-RIPE DUMY-RIPE MTU-NOC