PTK

BGP inherited
Cluster stats
Netblocks9 · 273 IPv4 addresses
Registered in Netherlands (5) · Russia (3)
All fragments 49 blocks across 12 clusters
Cluster ID208925525
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names 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
195.208.208.186/32 PTK PEERINGDB ASSIGNED ● high
83.167.201.36/30 PTK RIPE ASSIGNED PA ● low
85.146.192.112/30 PTK RIPE ASSIGNED PA ● low
85.146.196.124/30 PTK RIPE ASSIGNED PA ● low
85.146.223.132/30 PTK RIPE ASSIGNED PA ● low
85.146.242.152/30 PTK RIPE ASSIGNED PA ● low
195.131.21.0/24 PTK-NET RIPE ASSIGNED PA ● low
217.27.138.8/30 PTK-Net RIPE ASSIGNED PA ● low
2a00:18c8:3e23::/48 PTK RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PTK” — 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.
Combined view of all 12 name-family clusters →

Network trust

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

These blocks are registered to PTK 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.

195.131.21.0/24 /24 authorized for AS12714 — PJSC MegaFon

NIC Handles

ARTX-RIPE-MNT AS47618 DUMY-RIPE DUMY-RIPE TI-MNT TNF-MNT