rirtracker

IPv4 range · 1,024 addresses

213.109.104.0/22

Now

RIPE NCC statistics
Allocated (dated 2009-09-09) (CZ), in the latest file
Registry
RIPE NCC
Holder
MNT-EMERALD
From
RDAP, looked up 2026-11-07 18:20 UTC

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-11-05 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline (2)

Every change the tracker has found, newest first. It covers ARIN from 2008-12-01, the RIPE NCC from 2010-04-23, APNIC from 2008-02-15, LACNIC from 2012-06-29 and AFRINIC from 2012-10-03.

2026-11-05 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: iAge Technologies, Inc. (RIPE NCC) to Emerald Group s.r.o. (RIPE NCC)
From
iAge Technologies, Inc. RIPE NCC
To
Emerald Group s.r.o. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from iAge Technologies, Inc. (RIPE NCC) to Emerald Group s.r.o. (RIPE NCC) on 2026-11-05 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (2) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-11-05 19:00 UTC, iAge Technologies, Inc. (RIPE NCC) to Emerald Group s.r.o. (RIPE NCC); resources moved: 213.109.104.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-11-04 (produced 2026-11-04T22:59:59+00:00), before the change: assigned (dated 2009-09-09) source · retrieved
2024-01-03 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Programniy Region AO (RIPE NCC) to iAge Technologies, Inc. (RIPE NCC)
From
Programniy Region AO RIPE NCC
To
iAge Technologies, Inc. RIPE NCC
Piece of
213.109.96.0/20: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Programniy Region AO (RIPE NCC) to iAge Technologies, Inc. (RIPE NCC) on 2024-01-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-01-03 19:00 UTC, Programniy Region AO (RIPE NCC) to iAge Technologies, Inc. (RIPE NCC); resources moved: 213.109.104.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-01-02 (produced 2024-01-02T22:59:59+00:00), before the change: assigned (dated 2009-09-09) source · retrieved
  3. After RIPE NCC delegated statistics 2024-01-03 (produced 2024-01-03T22:59:59+00:00), after the change: assigned (dated 2009-09-09) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2016-01-04RIPE NCC213.109.96.0/20Transfer logIntra-RIPE NCC transfer

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer213.109.104.0/22 iAge Technologies, Inc. RIPE NCCEmerald Group s.r.o. RIPE NCC
RIPE NCCResource transfer213.109.104.0/22 Programniy Region AO RIPE NCCiAge Technologies, Inc. RIPE NCC
RIPE NCCResource transfer213.109.96.0/20 Prolead Ltd. RIPE NCCProgramniy Region PAO RIPE NCC

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv4 range (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). A transfer between two registries is in both logs.

RDAP lookups

Looked upWhyRegistryHandleOrganizationStatusLast changed
After 24 hours RIPE NCC213.109.104.0 - 213.109.104.255MNT-EMERALDactive2026-11-06
First seen RIPE NCC213.109.104.0 - 213.109.107.255MNT-EMERALDactive2026-11-05

Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.

This page as data: ip/213.109.104.0-213.109.107.255.json