DTAG-TECHNISCHER-SERVICE-VPNCL-IPT

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks7
IPv6 1 prefix (largest 2003:8:9800::/56)
All fragments 9 blocks across 2 clusters
Cluster ID228033214
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

9 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-08-23

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.56.248/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
62.153.58.0/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
62.153.58.136/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
62.153.59.72/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
62.153.60.192/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
62.153.66.56/29 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED PA ● low
2003:8:9800::/56 DTAG-TECHNISCHER-SERVICE-VPNCL-IPT RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

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

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE