TIMOSCHAFFERT
Cluster stats
Netblocks12
Cluster ID191671533
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
185.1.14.152/32 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
185.1.155.103/32 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2001:7f8:12e::20:7530:1/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2602:fed2:fff:ffff:6::10e/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0c:b641:701:0:a5:20:7530:1/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::205/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::20d/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:22::140/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::1d1/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::253/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:32::127/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:46::174/128 TIMOSCHAFFERT PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS207530