rirtracker

IPv4 range · 256 addresses

84.234.113.0/24

Now

RIPE NCC statistics
Assigned (dated 2004-11-24) on 2026-10-09 (PL)
Registry
RIPE NCC
Holder
PLJ TELECOM sp. z o.o.
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-03-27 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-03-27 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Jacek Dudek trading as "Prestiz" (RIPE NCC) to PLJ TELECOM sp. z o.o. (RIPE NCC)
From
Jacek Dudek trading as "Prestiz" RIPE NCC
To
PLJ TELECOM sp. z o.o. RIPE NCC
Piece of
84.234.112.0/23: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Jacek Dudek trading as "Prestiz" (RIPE NCC) to PLJ TELECOM sp. z o.o. (RIPE NCC) on 2026-03-27 19:00 UTC. The registration changed hands; it is not a new allocation from RIPE NCC.

Evidence (3) · classifier 1.1.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-03-27 19:00 UTC, Jacek Dudek trading as "Prestiz" (RIPE NCC) to PLJ TELECOM sp. z o.o. (RIPE NCC); resources moved: 84.234.113.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-03-26 (produced 2026-03-26T22:59:59+00:00), before the change: assigned (dated 2004-11-24) source · retrieved
  3. After RIPE NCC delegated statistics 2026-03-27 (produced 2026-03-27T22:59:59+00:00), after the change: assigned (dated 2004-11-24) source · retrieved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer84.234.113.0/24 Jacek Dudek trading as "Prestiz" RIPE NCCPLJ TELECOM sp. z o.o. RIPE NCC
RIPE NCCResource transfer84.234.112.0/20 Proqel Sp.z.o.o. RIPE NCCPrestiz Jacek Dudek RIPE NCC

Every record in the ARIN and RIPE NCC transfer logs that moved any part of this IPv4 range (ARIN's go back to 2009, the RIPE NCC's to 2012). A transfer between two registries is in both logs.

RDAP lookups

Not looked up. The tracker queries RDAP for changes as they're reported (on first sight, after 24 hours and after seven days); older changes aren't looked up because today's RDAP says nothing about the past.

This page as data: ip/84.234.113.0-84.234.113.255.json