PORTSMOUTH

BGP inherited
Cluster stats
Netblocks10
All fragments 43 blocks across 24 clusters
Cluster ID210474125
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.121.71.232/29 PORTSMOUTH RIPE ASSIGNED PA ● low
86.188.217.112/29 PORTSMOUTH RIPE ASSIGNED PA ● low
109.159.207.128/27 PORTSMOUTH RIPE ASSIGNED PA ● low
194.74.3.248/29 PORTSMOUTH RIPE ASSIGNED PA ● low
213.123.57.224/27 PORTSMOUTH RIPE LIR-PARTITIONED PA ● low
217.38.6.200/29 PORTSMOUTH RIPE ASSIGNED PA ● low
217.38.27.80/29 PORTSMOUTH RIPE ASSIGNED PA ● low
2a00:2381:2b7:1000::/56 PORTSMOUTH RIPE ASSIGNED ● low
2a00:2381:2b7:1500::/56 PORTSMOUTH RIPE ASSIGNED ● low
2a00:2381:3405:200::/56 PORTSMOUTH RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PORTSMOUTH” — 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.
Combined view of all 24 name-family clusters →
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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE