Top Connect
Cluster stats
Netblocks13
All fragments 52 blocks across 4 clusters
Cluster ID192331552
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

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

IP Ranges (13)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.137.179.19/32 Top Connect PEERINGDB ASSIGNED ● high
213.184.52.240/32 Top Connect PEERINGDB ASSIGNED ● high
77.240.240.0/27 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.240.32/27 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.240.64/26 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.240.128/25 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.241.0/27 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.241.32/28 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.241.80/29 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.241.96 – 77.240.241.119 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.243.0/28 TOP-CONNECT RIPE ASSIGNED PA ● low
77.240.245.0/27 TOP_CONNECT-NET RIPE ASSIGNED PA ● low
77.240.249.0/27 TOP_CONNECT-NET RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS42300 DUMY-RIPE DUMY-RIPE MNT-TOP_CONNECT MNT-TOP_CONNECT-SUBIP