SETCOMP

BGP inherited
Cluster stats
Netblocks8 · 3,096 IPv4 addresses
Cluster ID209551272
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-12

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.177.208.128/27 SETCOMP-NET RIPE ASSIGNED PA ● low
88.220.120.0/22 SETCOMP-NET RIPE ASSIGNED PA ● low
88.220.128.0/23 SETCOMP-NET RIPE ASSIGNED PA ● low
88.220.132.0/23 SETCOMP-NET RIPE ASSIGNED PA ● low
195.117.64.0/24 SETCOMP RIPE ASSIGNED PA ● low
195.117.141.0/24 SETCOMP RIPE ASSIGNED PA ● low
217.98.102.0/24 SETCOMP RIPE ASSIGNED PA ● low
217.98.251.0/24 SETCOMP RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (3)

These blocks are registered to SETCOMP but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

88.220.120.0/22 /22 authorized for AS20804 — Exatel S.A.
88.220.128.0/23 /23 authorized for AS20804 — Exatel S.A.
88.220.132.0/23 /23 authorized for AS20804 — Exatel S.A.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-EXATEL TPNET