PRIVEX-RENTED-SPACE

Data as of 2026-07-26
BGP inherited
Limited data: only 3 ranges found registered under this exact name. This may not reflect the organisation's full internet footprint — many companies' web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
Netblocks3
IPv6 3 prefixes (largest 2a07:e02:1100::/40)
Cluster ID216401574
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

IP Ranges (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a07:e02:1001::/48 PRIVEX-RENTED-SPACE RIPE ASSIGNED ● low
2a07:e02:1010::/44 PRIVEX-RENTED-SPACE RIPE ASSIGNED ● low
2a07:e02:1100::/40 PRIVEX-RENTED-SPACE RIPE ASSIGNED ● low

IPv6 ranges (3)

Network trust

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

These blocks are registered to PRIVEX-RENTED-SPACE 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.

2a07:e02:1100::/40 /40 authorized for AS63023 — GTHost

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-PRIVEX