rirtracker

IPv4 range · 256 addresses

84.38.3.0/24

Now

RIPE NCC statistics
Assigned (dated 2012-05-31) on 2026-10-09 (RU)
Registry
RIPE NCC
Holder
Gbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr"
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-10 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-03-10 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Get-Net LLC (RIPE NCC) to Gbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr" (RIPE NCC)
From
Get-Net LLC RIPE NCC
To
Gbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr" RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Get-Net LLC (RIPE NCC) to Gbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr" (RIPE NCC) on 2026-03-10 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-10 19:00 UTC, Get-Net LLC (RIPE NCC) to Gbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr" (RIPE NCC); resources moved: 84.38.3.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-03-09 (produced 2026-03-09T22:59:59+00:00), before the change: assigned (dated 2012-05-31) source · retrieved
  3. After RIPE NCC delegated statistics 2026-03-10 (produced 2026-03-10T22:59:59+00:00), after the change: assigned (dated 2012-05-31) source · retrieved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer84.38.3.0/24 Get-Net LLC RIPE NCCGbuz Sk "Meditsinskiy Informatsionno-Analiticheskiy Tsentr" RIPE NCC
RIPE NCCResource transfer84.38.0.0/22 RED-CODE LLC RIPE NCCGet-Net LLC 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.38.3.0-84.38.3.255.json