tim427.net
Cluster stats
Netblocks12
Cluster ID193384570
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

Footprint over time

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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.44.187.104/32 tim427.net PEERINGDB ASSIGNED ● high
80.249.210.60/32 tim427.net PEERINGDB ASSIGNED ● high
185.1.14.145/32 tim427.net PEERINGDB ASSIGNED ● high
185.1.138.23/32 tim427.net PEERINGDB ASSIGNED ● high
185.1.160.81/32 tim427.net PEERINGDB ASSIGNED ● high
185.1.222.25/32 tim427.net PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:21:4380:1/128 tim427.net PEERINGDB ASSIGNED ● high
2001:7f8:b7::a521:4380:1/128 tim427.net PEERINGDB ASSIGNED ● high
2001:7f8:109::3:456c:1/128 tim427.net PEERINGDB ASSIGNED ● high
2001:7f8:10f::3:456c:81/128 tim427.net PEERINGDB ASSIGNED ● high
2001:7f8:12e::21:4380:1/128 tim427.net PEERINGDB ASSIGNED ● high
2a0c:b641:700:0:a5:21:4380:1/128 tim427.net PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS214380