rirtracker

IPv4 range · 1,024 addresses

216.162.44.0/22

Now

RIPE NCC statistics
Allocated (dated 2016-07-01) on 2026-10-09 (GB)
Registry
RIPE NCC
Holder
Local NCC Ltd.
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Inter-RIR transfer into RIPE NCC

Reported
2026-02-02 (RIPE NCC)
Confidence
Confirmed
Inventory
Transferred into RIPE NCC administration; not a new issuance

Timeline since 2026-01-01 (1)

2026-02-02 RIPE NCC Transfer log Inter-RIR transfer into RIPE NCC Confirmed
Transfer log
Transfer: (no name) (ARIN) to Local NCC Ltd. (RIPE NCC)
From
(no name given) ARIN
To
Local NCC Ltd. RIPE NCC
Inventory
Transferred into RIPE NCC administration; not a new issuance

RIPE NCC's transfer log records a transfer from an unnamed organization (ARIN) to Local NCC Ltd. (RIPE NCC) on 2026-02-02 19:00 UTC: it came to RIPE NCC from ARIN. It was already issued by another registry, so this is not a new issuance.

Evidence (3) · classifier 1.1.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-02-02 19:00 UTC, (no name) (ARIN) to Local NCC Ltd. (RIPE NCC); resources moved: 216.162.44.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-02-01 (produced 2026-02-01T22:59:59+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2026-02-02 (produced 2026-02-02T22:59:59+00:00), after the change: allocated (dated 2016-07-01) source · retrieved

Transfer records (4)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer216.162.44.0/22 (no name given) ARINLocal NCC Ltd. RIPE NCC
ARINResource transfer216.162.44.0/22 DOJ-USMS ARINLocal NCC Ltd RIPE NCC
ARINMerger acquisition216.162.40.0/21 Micfo, LLC. ARINU.S. Marshals Service in accordance with the Final Order of Forfeiture ARIN
ARINResource transfer216.162.40.0/21 iNET Systems Corp. ARINMicfo, LLC. ARIN

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/216.162.44.0-216.162.47.255.json