PHOENIX-IT-SERVICES

BGP inherited
Cluster stats
Netblocks6
Registered in France (1) · United Kingdom (1)
All fragments 7 blocks across 2 clusters
Cluster ID210177665
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
86.66.35.16/29 PHOENIX-IT-SERVICES RIPE ASSIGNED PA ● low
217.41.244.48/28 PHOENIX-IT-SERVICES RIPE ASSIGNED PA ● low
2a00:2381:3c6::/48 PHOENIX-IT-SERVICES RIPE AGGREGATED-BY-LIR ● low
2a00:2381:3c6:100::/56 PHOENIX-IT-SERVICES RIPE ASSIGNED ● low
2a00:2381:9ce::/48 PHOENIX-IT-SERVICES RIPE AGGREGATED-BY-LIR ● low
2a00:2381:f073::/48 PHOENIX-IT-SERVICES RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

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

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT