AC Systemy Sp. z o.o.

AC Systemy Sp. z o. o.
Data as of 2026-09-13
BGP inherited
This organisation
Netblocks12
IPv6 6 prefixes (largest 2001:678:3ac::155/128)
Also registered under this name 28 netblocks across 2 separate records
Record ID242143800
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.46.144.155/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
89.46.144.196/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
178.216.40.133/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
178.216.41.224/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
195.149.232.168/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
195.191.170.17/32 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2001:678:3ac::155/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2001:678:3ac::f86/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2001:7f8:27::20:5679:1/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2001:7f8:5b::133/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2001:7f8:5b::566/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high
2a10:f780::17/128 AC Systemy Sp. z o. o. PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Footprint over time

12 weekly snapshots · JSON
12 +4 netblocks since 2026-07-05
2026-07-05 peak 12 2026-09-13

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (8 of 12)
No discrepancies found among checked blocks.

NIC Handles

AS205679