PORTMAN

BGP inherited
Cluster stats
Netblocks6
All fragments 10 blocks across 5 clusters
Cluster ID205253896
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.143.114.248/29 PORTMAN RIPE ASSIGNED PA ● low
178.18.116.136/29 Portman_Group_Ltd RIPE ASSIGNED PA ● low
178.18.116.144/30 Portman_Group_Ltd RIPE ASSIGNED PA ● low
193.133.26.128/26 PORTMAN-NET RIPE ASSIGNED PA ● low
193.195.150.232/29 PORTMAN RIPE ASSIGNED PA ● low
195.59.29.8/29 PORTMAN RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

AI AS1849-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE VODAFONE-WORLDWIDE-MNTNER