REMOTE-ACCESS

BGP inherited
Cluster stats
Netblocks4 · 2,076 IPv4 addresses
All fragments 5 blocks across 2 clusters
Cluster ID209237074
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.74.123.0 – 80.74.127.255 Remote-Access RIPE ASSIGNED PA ● low
91.143.234.0/23 REMOTE-ACCESS RIPE ASSIGNED PA ● low
94.188.155.0/24 REMOTE-ACCESS RIPE ASSIGNED PA ● low
212.96.209.32/27 Remote_access_Net RIPE ASSIGNED PA ● low

Network trust

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

These blocks are registered to REMOTE-ACCESS 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.

80.74.123.0 – 80.74.127.255 /22 authorized for AS25003 — Internet Binat Ltd
91.143.234.0/23 /23 authorized for AS25003 — Internet Binat Ltd
94.188.155.0/24 /24 authorized for AS25003 — Internet Binat Ltd

NIC Handles

DUMY-RIPE DUMY-RIPE QOS-ISP-MNT ROSTELECOM-MNT