IXDNS

Handle
Cluster stats
Netblocks10
All fragments 54 blocks across 8 clusters
Cluster ID207720776
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

4 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.194.200/32 IXDNS PEERINGDB ASSIGNED ● high
80.249.209.212/32 IXDNS PEERINGDB ASSIGNED ● high
185.79.213.8/32 IXDNS PEERINGDB ASSIGNED ● high
194.85.177.21/32 IXDNS PEERINGDB ASSIGNED ● high
194.190.119.32/32 IXDNS PEERINGDB ASSIGNED ● high
2001:7f8::a591:0:1/128 IXDNS PEERINGDB ASSIGNED ● high
2001:7f8:1::a504:2385:1/128 IXDNS PEERINGDB ASSIGNED ● high
2001:7f8:20:801::119:32/128 IXDNS PEERINGDB ASSIGNED ● high
2001:7f8:20:901::177:21/128 IXDNS PEERINGDB ASSIGNED ● high
2a01:7640:9400::8/128 IXDNS PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “IXDNS” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

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

AS42385