D VOIPTELECOM

BGP inherited
Cluster stats
Netblocks8
Cluster ID211526397
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
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
2a01:7a7:2:1fa3::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:1fa5::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:202e::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:203f::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:204a::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:23c3::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:23f0::/64 D VOIPTELECOM RIPE ASSIGNED ● high
2a01:7a7:2:2513::/64 D VOIPTELECOM RIPE ASSIGNED ● high

Possibly related to this organisation

what's this?
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.
  • Voiptelecom via Orion Telekom Tim d.o.o.Beograd sub-allocation

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

DUMY-RIPE DUMY-RIPE FGK-MNT ORG-DV51-RIPE