AR_SOLUTION

Data as of 2026-09-06
Handle
This organisation
Netblocks10 · 256 IPv4 addresses
IPv6 9 prefixes (largest 2a0e:8f01:1000:10::10e/128)
Record ID238781274
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a0e:8f01:1000:3::117/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:3::144/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::171/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::17c/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:10::10e/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::221/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:16::12d/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:16::157/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::19a/128 AR_SOLUTION PEERINGDB ASSIGNED ● high
185.2.49.0/24 AR-Solution RIPE ASSIGNED PA ● low

IPv6 ranges (9)

Footprint over time

4 weekly snapshots · JSON
10 +3 netblocks since 2026-08-16
2026-08-16 peak 10 2026-09-06

Network trust

what's this?
RPKI hygiene: F how networks compare →
10.0% of checked blocks have valid RPKI ROA coverage (1 of 10)
RPKI-inferred operator OVH SAS
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

AR39046-RIPE AS218984 DUMY-RIPE DUMY-RIPE hk-larus-1-mnt