IPBRX-ACCESS-Equipments

Handle
Cluster stats
Netblocks7 · 4,601 IPv4 addresses
Cluster ID208879255
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.10.112.0/22 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
80.10.118.0/24 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
80.10.120.0/21 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
193.251.96.0/24 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
193.252.146.0/24 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
193.252.253.0/24 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low
193.253.139.0 – 193.253.140.255 IPBRX-ACCESS-Equipments RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
42.9% of checked blocks have valid RPKI ROA coverage (3 of 7)
RPKI-inferred operator Orange S.A.
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE FT-BRX