dtms converting communication

Data as of 2026-09-27
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2001:7f8:19:1::3208:1/128)
Record ID246698953
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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.194.58/32 dtms converting communication PEERINGDB ASSIGNED ● high
80.81.194.239/32 dtms converting communication PEERINGDB ASSIGNED ● high
185.1.210.154/32 dtms converting communication PEERINGDB ASSIGNED ● high
193.178.185.134/32 dtms converting communication PEERINGDB ASSIGNED ● high
2001:7f8::3208:0:1/128 dtms converting communication PEERINGDB ASSIGNED ● high
2001:7f8::3208:0:2/128 dtms converting communication PEERINGDB ASSIGNED ● high
2001:7f8:19:1::3208:1/128 dtms converting communication PEERINGDB ASSIGNED ● high
2001:7f8:3d::3208:0:1/128 dtms converting communication PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

14 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-09-27

Network trust

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

NIC Handles

AS12808