DKTEL

Handle
Cluster stats
Netblocks8
Registered in Russia (3) · AG (2)
All fragments 16 blocks across 9 clusters
Cluster ID213184477
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

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
109.239.136.209/32 DKTEL PEERINGDB ASSIGNED ● high
178.18.226.5/32 DKTEL PEERINGDB ASSIGNED ● high
185.0.12.113/32 DKTEL PEERINGDB ASSIGNED ● high
185.232.60.88/32 DKTEL PEERINGDB ASSIGNED ● high
195.208.209.235/32 DKTEL PEERINGDB ASSIGNED ● high
2001:7f8:20:101::209:235/128 DKTEL PEERINGDB ASSIGNED ● high
2001:b28:3ff::136:209/128 DKTEL PEERINGDB ASSIGNED ● high
2a03:5f80:4::226:5/128 DKTEL PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DKTEL” — 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: C how networks compare →
62.5% of checked blocks have valid RPKI ROA coverage (5 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS199624