Telemax X
TelemaxX
Cluster stats
Netblocks9
All fragments 152 blocks across 3 clusters
Cluster ID193028227
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.193.198/32 TelemaxX PEERINGDB ASSIGNED ● high
185.1.61.31/32 TelemaxX PEERINGDB ASSIGNED ● high
2001:7f8::322b:0:2/128 TelemaxX PEERINGDB ASSIGNED ● high
2001:7f8:9d::31:1/128 TelemaxX PEERINGDB ASSIGNED ● high
5.7.248.40/29 TELEMAXX-NET RIPE ASSIGNED PA ● low
62.54.111.168/29 TELEMAXX-NET RIPE ASSIGNED PA ● low
62.159.105.32/29 TELEMAXX-IPC3-KARLSRUHE-NET RIPE ASSIGNED PA ● low
212.18.206.16/30 TELEMAXX-NET RIPE ASSIGNED PA ● low
2003:e8:4014::/48 TELEMAXX-IPC3-KARLSRUHE-NET RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to TelemaxX but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2003:e8:4014::/48 /48 authorized for AS3320 — Deutsche Telekom AG

NIC Handles

AS12843 DTAG-NIC DUMY-RIPE DUMY-RIPE MDA-Z SAARGATE-DE-MNT