PL-TKTELEKOM-CORE

BGP inherited
Cluster stats
Netblocks7 · 2,425 IPv4 addresses
All fragments 8 blocks across 2 clusters
Cluster ID209265237
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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
88.199.212.0/24 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.218.0/25 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.219.0/24 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.232.0/22 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.236.0/24 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.237.0/24 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low
88.199.239.0/24 PL-TKTELEKOM-CORE RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PL TKTELEKOM CORE” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE NETIA-MNT