HAASE IT

Data as of 2026-11-15
BGP inherited
This organisation
Netblocks10
IPv6 6 prefixes (largest 2001:7f8:11c:1:0:5:7222:1/128)
Record ID273984233
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.0.30.85/32 HAASE IT PEERINGDB ASSIGNED ● high
185.1.59.213/32 HAASE IT PEERINGDB ASSIGNED ● high
185.1.147.57/32 HAASE IT PEERINGDB ASSIGNED ● high
195.60.91.147/32 HAASE IT PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:5:7222:1/128 HAASE IT PEERINGDB ASSIGNED ● high
2001:7f8:cc:333:0:5:7222:1/128 HAASE IT PEERINGDB ASSIGNED ● high
2001:7f8:11c:1:0:5:7222:1/128 HAASE IT PEERINGDB ASSIGNED ● high
2001:7f8:172:1:0:5:7222:1/128 HAASE IT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::1ff/128 HAASE IT PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:25::168/128 HAASE IT PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Footprint over time

12 weekly snapshots · JSON
10 +2 netblocks since 2026-08-30
2026-08-30 peak 10 2026-11-15

Network trust

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

NIC Handles

AS57222