Haima Network

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks10
IPv6 8 prefixes (largest 2001:ded:c000::54/128)
Record ID239857793
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
23.154.164.157/32 Haima Network PEERINGDB ASSIGNED ● high
195.60.92.71/32 Haima Network PEERINGDB ASSIGNED ● high
2001:ded:c000::54/128 Haima Network PEERINGDB ASSIGNED ● high
2404:f4c0:f70e:1980::202:335/128 Haima Network PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:20:2335:1/128 Haima Network PEERINGDB ASSIGNED ● high
2602:f429:31::1e/128 Haima Network PEERINGDB ASSIGNED ● high
2602:f919:90f:fffa::2023:35/128 Haima Network PEERINGDB ASSIGNED ● high
2602:f92a:1315::24/128 Haima Network PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::32/128 Haima Network PEERINGDB ASSIGNED ● high
2602:f93b:1a35:1311::71/128 Haima Network PEERINGDB ASSIGNED ● high

IPv6 ranges (8)

Footprint over time

11 weekly snapshots · JSON
10 +2 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-06

Network trust

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

NIC Handles

AS202335