B2B-FIX-SHPD-202601
Unresolved
Cluster stats
Netblocks7
All fragments 99 blocks across 36 clusters
Cluster ID194040886
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
188.75.192.0/20 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.208.0/23 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.210.0/23 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.212.0/23 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.214.0/23 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.220.0/22 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low
188.75.252.0/22 B2B-FIX-SHPD-202601 RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
42.9% of checked blocks have valid RPKI ROA coverage (3 of 7)
RPKI-inferred operator MTS PJSC
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MTU-NOC