Connect2IP
Cluster stats
Netblocks14
Cluster ID193387044
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.174/32 Connect2IP PEERINGDB ASSIGNED ● high
149.112.29.118/32 Connect2IP PEERINGDB ASSIGNED ● high
185.1.135.115/32 Connect2IP PEERINGDB ASSIGNED ● high
185.1.138.15/32 Connect2IP PEERINGDB ASSIGNED ● high
185.1.147.230/32 Connect2IP PEERINGDB ASSIGNED ● high
206.81.104.84/32 Connect2IP PEERINGDB ASSIGNED ● high
2001:504:125:e0::118/128 Connect2IP PEERINGDB ASSIGNED ● high
2001:7f8:17::891c:1/128 Connect2IP PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:3:5100:1/128 Connect2IP PEERINGDB ASSIGNED ● high
2001:7f8:d0::891c:1/128 Connect2IP PEERINGDB ASSIGNED ● high
2001:7f8:d9:1::891c:1/128 Connect2IP PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff:6::ed/128 Connect2IP PEERINGDB ASSIGNED ● high
2a0c:b641:700:0:a5:35:100:1/128 Connect2IP PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:46::191/128 Connect2IP PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: D how networks compare →
28.6% of checked blocks have valid RPKI ROA coverage (4 of 14)
No discrepancies found among checked blocks.

NIC Handles

AS35100