Connected sp. z o.o.

Connected sp. z o. o.
Data as of 2026-10-11
BGP inherited
This organisation
Netblocks6 · 17,152 IPv4 addresses
IPv6 2 prefixes (largest 2a00:1578::/29)
Also registered under this name 9 netblocks across 2 separate records
Record ID245618687
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 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 (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.175.128.0/24 Connected sp. z o. o. BGP ANNOUNCED ● high
91.230.120.0/24 Connected sp. z o. o. BGP ANNOUNCED ● high
93.159.128.0/18 Connected sp. z o. o. BGP ANNOUNCED ● high
2a00:1578::/29 Connected sp. z o. o. BGP ANNOUNCED ● high
185.1.120.0/24 Connected sp. z o. o. RIPE ASSIGNED PI ● low
2001:7f8:d6::/48 Connected sp. z o. o. RIPE ASSIGNED PI ● low

IPv6 ranges (2)

Footprint over time

16 weekly snapshots · JSON
8 -18 netblocks since 2026-07-05
2026-07-05 peak 26 2026-10-11

Network trust

what's this?
RPKI hygiene: C how networks compare →
62.5% of checked blocks have valid RPKI ROA coverage (5 of 8)
Possible discrepancies (1)

These blocks are registered to Connected sp. z o. o. 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.

83.175.128.0/24 /24 authorized for AS51648 — GIGAINTERNET Sp z o.o.

NIC Handles

AS49102 CONNECTED-MNT CONNECTED-MNT DUMY-RIPE DUMY-RIPE GIGA-MNT ORG-Ks27-RIPE RIPE-NCC-END-MNT RIPE-NCC-HM-MNT