rirtracker

IPv4 range · 65,536 addresses

160.86.0.0/16

Now

APNIC statistics
Allocated (dated 1992-04-29) (JP), in the latest file
Registry
APNIC
Holder
Sony Network Communication Inc.
From
APNIC's latest statistics and the latest transfer record

Latest change

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

Reported
2017-08-22 (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.

2017-08-22 ARIN Not in ARIN-Issued Inter-RIR transfer out of ARIN Confirmed
From
Intrusion Inc. ARIN
To
Sony Network Communication Inc. APNIC
Same transfer
APNIC recorded it too: APNIC, 2017-08-22.
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

ARIN's transfer log records a transfer from Intrusion Inc. (ARIN) to Sony Network Communication Inc. (APNIC) on 2017-08-22 15:15 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: 160.86.0.0/16 assigned on 2017-08-22, not listed on 2017-08-23 source · retrieved
  2. Transfer log Transfer log: RESOURCE_TRANSFER on 2017-08-22 15:15 UTC, Intrusion Inc. (ARIN) to Sony Network Communication Inc. (APNIC); resources moved: 160.86.0.0/16 source · retrieved
  3. Before ARIN delegated statistics 2017-08-21 (produced 2017-08-21T05:10:37+00:00), before the report: assigned (dated 1992-04-29) source · retrieved
  4. After ARIN delegated statistics 2017-08-23 (produced 2017-08-23T05:10:40+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
2017-08-22 APNIC Transfer log Inter-RIR transfer into APNIC Confirmed
Transfer log
Transfer: INTRU-3 (ARIN) to Japan Network Information Center/so-net (APNIC)
From
INTRU-3 ARIN
To
Japan Network Information Center/so-net APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2017-08-22. 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 INTRU-3 (ARIN) to Japan Network Information Center/so-net (APNIC) on 2017-08-22 04:33 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 2017-08-22 04:33 UTC, INTRU-3 (ARIN) to Japan Network Information Center/so-net (APNIC); resources moved: 160.86.0.0/16 source · retrieved
  2. Before APNIC delegated statistics 2017-08-22, before the change: not listed source · retrieved
  3. After APNIC delegated statistics 2017-08-23, after the change: allocated (dated 1992-04-29) 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 transfer160.86.0.0/16 Intrusion Inc. ARINSony Network Communication Inc. APNIC
APNICResource transfer160.86.0.0/16 INTRU-3 ARINJapan Network Information Center/so-net 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/160.86.0.0-160.86.255.255.json