rirtracker

IPv4 range · 2,048 addresses

194.29.192.0/21

Now

RIPE NCC statistics
Allocated (dated 2000-02-29) on 2026-10-09 (PL)
Registry
RIPE NCC
Holder
Geckonet 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-08-31 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-08-31 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Telia Cygate Oy (RIPE NCC) to Geckonet Sp. z o. o. (RIPE NCC)
From
Telia Cygate Oy RIPE NCC
To
Geckonet Sp. z o. o. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Telia Cygate Oy (RIPE NCC) to Geckonet Sp. z o. o. (RIPE NCC) on 2026-08-31 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-08-31 19:00 UTC, Telia Cygate Oy (RIPE NCC) to Geckonet Sp. z o. o. (RIPE NCC); resources moved: 194.29.192.0/21 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-08-30 (produced 2026-08-30T21:59:59+00:00), before the change: allocated (dated 2000-02-29) source · retrieved
  3. After RIPE NCC delegated statistics 2026-08-31 (produced 2026-08-31T21:59:59+00:00), after the change: allocated (dated 2000-02-29) source · retrieved

Transfer records (4)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer194.29.192.0/21 Telia Cygate Oy RIPE NCCGeckonet Sp. z o. o. RIPE NCC
RIPE NCCMerger acquisition194.29.192.0/21 Telia Inmics-Nebula Oy RIPE NCCTelia Cygate Oy RIPE NCC
RIPE NCCMerger acquisition194.29.192.0/21 Nebula Oy RIPE NCCTelia Inmics-Nebula Oy RIPE NCC
RIPE NCCResource transfer194.29.192.0/21 TelecityGroup Finland Oy RIPE NCCNebula Oy 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/194.29.192.0-194.29.199.255.json