ISSP

BGP inherited
Cluster stats
Netblocks6
Registered in Thailand (2) · Russia (1) · Ukraine (1)
All fragments 27 blocks across 21 clusters
Cluster ID209034542
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.19.60.33/32 ISSP PEERINGDB ASSIGNED ● high
116.206.112.9/32 ISSP PEERINGDB ASSIGNED ● high
2001:c38:8000::7654:1/128 ISSP PEERINGDB ASSIGNED ● high
2405:4000:3000:1::7654:1/128 ISSP PEERINGDB ASSIGNED ● high
83.149.210.32/28 ISSP RIPE ASSIGNED PA ● low
194.183.170.128/28 issp RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “ISSP” — 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 21 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: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS3058-MNT AS7654 DUMY-RIPE DUMY-RIPE LDC-UA-MNT