APSYSTEMSRL

BGP inherited
Cluster stats
Netblocks9
Cluster ID209035088
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

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.189.127.240/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
82.190.93.136/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
85.33.126.152/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
85.39.123.232/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
85.39.125.32/28 APSYSTEMSRL RIPE ASSIGNED PA ● low
85.39.125.48/28 APSYSTEMSRL RIPE ASSIGNED PA ● low
88.35.200.168/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
88.39.119.176/29 APSYSTEMSRL RIPE ASSIGNED PA ● low
88.39.144.80/29 APSYSTEMSRL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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.

NIC Handles

DUMY-RIPE DUMY-RIPE INTERB-MNT