rirtracker

IPv4 range · 65,536 addresses

159.75.0.0/16

Now

APNIC statistics
Allocated (dated 1992-03-17) (CN), in the latest file
Registry
APNIC
Holder
Oriental Power Holdings
From
APNIC's latest statistics and the latest transfer record

Latest change

Not in ARIN-Issued Inter-RIR transfer out of ARIN

Reported
2018-02-20 (ARIN)
Confidence
Confirmed
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

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.

2018-02-20 ARIN Not in ARIN-Issued Inter-RIR transfer out of ARIN Confirmed
From
Xcerra Corporation ARIN
To
Oriental Power Holdings APNIC
Same transfer
APNIC recorded it too: APNIC, 2018-02-20.
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

ARIN's transfer log records a transfer from Xcerra Corporation (ARIN) to Oriental Power Holdings (APNIC) on 2018-02-20 12:52 UTC: it left ARIN for APNIC. ARIN-Issued didn't list this change; it is not a new allocation and is not offered to ARIN applicants.

Evidence (4) · classifier 1.4.0,
  1. Statistics Not listed in ARIN-Issued; found by comparing ARIN's daily statistics: 159.75.0.0/16 assigned on 2018-02-20, not listed on 2018-02-21 source · retrieved
  2. Transfer log Transfer log: RESOURCE_TRANSFER on 2018-02-20 12:52 UTC, Xcerra Corporation (ARIN) to Oriental Power Holdings (APNIC); resources moved: 159.75.0.0/16 source · retrieved
  3. Before ARIN delegated statistics 2018-02-19 (produced 2018-02-19T06:10:25+00:00), before the report: assigned (dated 1992-03-17) source · retrieved
  4. After ARIN delegated statistics 2018-02-21 (produced 2018-02-21T06:09:03+00:00), after the report: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.4.0) current
2018-02-20 APNIC Transfer log Inter-RIR transfer into APNIC Confirmed
Transfer log
Transfer: LCA-1 (ARIN) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC)
From
LCA-1 ARIN
To
Tencent Cloud Computing (Beijing) Co., Ltd APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2018-02-20. Lists that cover every registry show it there.
Inventory
Transferred into APNIC administration; not a new issuance

APNIC's transfer log records a transfer from LCA-1 (ARIN) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC) on 2018-02-20 05:50 UTC: it came to APNIC from ARIN. It was already issued by another registry, so this is not a new issuance.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2018-02-20 05:50 UTC, LCA-1 (ARIN) to Tencent Cloud Computing (Beijing) Co., Ltd (APNIC); resources moved: 159.75.0.0/16 source · retrieved
  2. Before APNIC delegated statistics 2018-02-20, before the change: not listed source · retrieved
  3. After APNIC delegated statistics 2018-02-21, after the change: allocated (dated 1992-03-17) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into APNIC, confirmed (classifier 1.4.0) current

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
ARINResource transfer159.75.0.0/16 Xcerra Corporation ARINOriental Power Holdings APNIC
APNICResource transfer159.75.0.0/16 LCA-1 ARINTencent Cloud Computing (Beijing) Co., Ltd APNIC

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

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/159.75.0.0-159.75.255.255.json