MTS PJSC

MTS-SPB-HOME-P8
BGP inherited
Cluster stats
Netblocks9 · 2,295 IPv4 addresses
All fragments 58 blocks across 8 clusters
Cluster ID209959303
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
94.72.51.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.52.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.53.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.54.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.55.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.56.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.57.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.58.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low
94.72.59.0/24 MTS-SPB-HOME-P8 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MTS SPB HOME” — 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 LANCK-MNT