Telkab sp. z o.o.

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks10 · 8,706 IPv4 addresses
IPv6 1 prefix (largest 2a0d:1900::/29)
Record ID245942439
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 3 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
89.46.144.52/32 Telkab sp. z o.o. PEERINGDB ASSIGNED ● high
109.197.96.0/21 Telkab sp. z o.o. BGP ANNOUNCED ● high
109.207.144.0/20 Telkab sp. z o.o. BGP ANNOUNCED ● high
185.167.32.0/22 Telkab sp. z o.o. BGP ANNOUNCED ● high
192.166.32.0/22 Telkab sp. z o.o. BGP ANNOUNCED ● high
195.182.218.232/32 Telkab sp. z o.o. PEERINGDB ASSIGNED ● high
195.191.180.0/23 Telkab sp. z o.o. BGP ANNOUNCED ● high
192.166.32.0/23 Telkab sp. z o.o. RIPE ASSIGNED PA ● medium
192.166.34.0/23 Telkab sp. z o.o. RIPE ASSIGNED PA ● medium
2a0d:1900::/29 Telkab sp. z o.o. RIPE ALLOCATED-BY-RIR ● low

IPv6 ranges (1)

Footprint over time

16 weekly snapshots · JSON
15 0 netblocks since 2026-07-05
2026-07-05 peak 15 2026-10-11

Network trust

what's this?
RPKI hygiene: B how networks compare →
93.3% of checked blocks have valid RPKI ROA coverage (14 of 15)
No discrepancies found among checked blocks.

NIC Handles

AS50661 AS50661 DUMY-RIPE DUMY-RIPE ORG-TSZO60-RIPE RIPE-NCC-END-MNT RIPE-NCC-HM-MNT pl-telkab-1-mnt pl-telkab-1-mnt