rirtracker

IPv4 range · 4,096 addresses

168.113.128.0/20

Now

RIPE NCC statistics
Allocated (dated 1994-03-24) on 2026-10-09 (RU)
Registry
RIPE NCC
Holder
Next LLC
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-10-02 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-10-02 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Andrei Zaitsev (RIPE NCC) to Next LLC (RIPE NCC)
From
Andrei Zaitsev RIPE NCC
To
Next LLC RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Andrei Zaitsev (RIPE NCC) to Next LLC (RIPE NCC) on 2026-10-02 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-10-02 19:00 UTC, Andrei Zaitsev (RIPE NCC) to Next LLC (RIPE NCC); resources moved: 168.113.128.0/20 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-10-01 (produced 2026-10-01T21:59:59+00:00), before the change: allocated (dated 1994-03-24) source · retrieved
  3. After RIPE NCC delegated statistics 2026-10-02 (produced 2026-10-02T21:59:59+00:00), after the change: allocated (dated 1994-03-24) source · retrieved

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-06-24RIPE NCC168.113.0.0/16Transfer logTransfer into RIPE NCC
2026-06-24ARIN168.113.0.0/16Not in ARIN-IssuedTransfer out of ARIN

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer168.113.128.0/20 Andrei Zaitsev RIPE NCCNext LLC RIPE NCC
RIPE NCCResource transfer168.113.0.0/16 (no name given) ARINWireless Ltd RIPE NCC
ARINResource transfer168.113.0.0/16 Synet Inc. ARINWireless Ltd 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/168.113.128.0-168.113.143.255.json