rirtracker

IPv4 range · 1,024 addresses

113.20.156.0/22

Now

RIPE NCC statistics
Allocated (dated 2016-01-20) (GB), in the latest file
Registry
RIPE NCC
Holder
ORG-ZL31-RIPE
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of APNIC

Reported
2021-12-21 (APNIC)
Confidence
Confirmed
Inventory
Transferred out of APNIC administration; not offered to APNIC applicants

Timeline (5)

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.

2021-12-21 APNIC Transfer log Inter-RIR transfer out of APNIC Confirmed
Transfer log
Transfer: Zeniva LLC (APNIC) to ORG-ZL31-RIPE (RIPE NCC)
From
Zeniva LLC APNIC
To
ORG-ZL31-RIPE RIPE NCC
Same transfer
The RIPE NCC recorded it too: RIPE NCC, 2021-12-20.
Inventory
Transferred out of APNIC administration; not offered to APNIC applicants

APNIC's transfer log records a transfer from Zeniva LLC (APNIC) to ORG-ZL31-RIPE (RIPE NCC) on 2021-12-20 19:04 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2021-12-20 19:04 UTC, Zeniva LLC (APNIC) to ORG-ZL31-RIPE (RIPE NCC); resources moved: 103.206.232.0/22, 113.20.156.0/22 source · retrieved
  2. Before APNIC delegated statistics 2021-12-21, before the change: allocated (dated 2016-01-20) source · retrieved
  3. After APNIC delegated statistics 2021-12-22, after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.4.0) current
2021-12-20 RIPE NCC Transfer log Inter-RIR transfer into the RIPE NCC Confirmed
Transfer log
Transfer: (no name) (APNIC) to SYN LTD (RIPE NCC)
From
(no name given) APNIC
To
SYN LTD RIPE NCC
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2021-12-21. Lists that cover every registry show it there.
Inventory
Transferred into RIPE NCC administration; not a new issuance

The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to SYN LTD (RIPE NCC) on 2021-12-20 19:00 UTC: it came to the RIPE NCC from APNIC. 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 2021-12-20 19:00 UTC, (no name) (APNIC) to SYN LTD (RIPE NCC); resources moved: 113.20.156.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-12-19 (produced 2021-12-19T22:59:00+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2021-12-20 (produced 2021-12-20T22:59:00+00:00), after the change: allocated (dated 2016-01-20) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.4.0) current
2016-01-20 APNIC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
113.20.156.0/22 reserved on 2016-01-20, allocated on 2016-01-21
Inventory
Likely issued from APNIC-controlled inventory

No transfer record matches. APNIC's statistics show it reserved on 2016-01-20 and allocated (dated 2016-01-20) on 2016-01-21. The tracker saw this range removed from registration on 2015-01-14 (113.20.156.0/22), so it appears to have been issued again from APNIC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 113.20.156.0/22 reserved on 2016-01-20, allocated on 2016-01-21 source · retrieved
  2. Before APNIC delegated statistics 2016-01-20, before the change: reserved source · retrieved
  3. After APNIC delegated statistics 2016-01-21, after the change: allocated (dated 2016-01-20) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current
2015-01-14 APNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
113.20.156.0/22 allocated on 2015-01-14, reserved on 2015-01-15
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2016-01-14. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2008-10-17) on 2015-01-14 and reserved on 2015-01-15. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2016-01-14. That is what APNIC has done, not a rule it states. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 113.20.156.0/22 allocated on 2015-01-14, reserved on 2015-01-15 source · retrieved
  2. Before APNIC delegated statistics 2015-01-14, before the change: allocated (dated 2008-10-17) source · retrieved
  3. After APNIC delegated statistics 2015-01-15, after the change: reserved source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2008-10-17 APNIC + Registered Unresolved change Observed only
Statistics
113.20.156.0/22 not listed on 2008-10-17, allocated on 2008-10-18
Inventory
Inventory effect unknown

No transfer record matches. APNIC's statistics show it not listed on 2008-10-17 and allocated (dated 2008-10-17) on 2008-10-18. It wasn't in APNIC's statistics before, so it wasn't APNIC's unissued inventory; it may have come from another registry in a transfer not yet in the log.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 113.20.156.0/22 not listed on 2008-10-17, allocated on 2008-10-18 source · retrieved
  2. Before APNIC delegated statistics 2008-10-17, before the change: not listed source · retrieved
  3. After APNIC delegated statistics 2008-10-18, after the change: allocated (dated 2008-10-17) source · retrieved
Classification history for this change (4 versions)
  1. : Unresolved change, observed only (classifier 1.3.0)
  2. : Unresolved change, observed only (classifier 1.3.1)
  3. : Unresolved change, observed only (classifier 1.3.2)
  4. : Unresolved change, observed only (classifier 1.4.0) current

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer113.20.156.0/22 Zeniva LLC APNICORG-ZL31-RIPE RIPE NCC
RIPE NCCResource transfer113.20.156.0/22 (no name given) APNICSYN LTD RIPE NCC

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/113.20.156.0-113.20.159.255.json