rirtracker

IPv4 range · 1,024 addresses

194.26.72.0/22

Now

APNIC statistics
Allocated (dated 2018-07-24) (HK), in the latest file
Registry
APNIC
Holder
Not looked up
From
APNIC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of the RIPE NCC

Reported
2020-12-09 (RIPE NCC)
Confidence
Confirmed
Inventory
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants

Timeline (4)

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.

2020-12-09 RIPE NCC Transfer log Inter-RIR transfer out of the RIPE NCC Confirmed
Transfer log
Transfer: Pishgaman Dadeh Afzar Company Ltd. (RIPE NCC) to (no name) (APNIC)
From
Pishgaman Dadeh Afzar Company Ltd. RIPE NCC
To
(no name given) APNIC
Same transfer
APNIC recorded it too: APNIC, 2020-12-09.
Inventory
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants

The RIPE NCC's transfer log records a transfer from Pishgaman Dadeh Afzar Company Ltd. (RIPE NCC) to an unnamed organization (APNIC) on 2020-12-09 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2020-12-09 19:00 UTC, Pishgaman Dadeh Afzar Company Ltd. (RIPE NCC) to (no name) (APNIC); resources moved: 194.26.72.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-12-08 (produced 2020-12-08T22:59:00+00:00), before the change: allocated (dated 2018-07-24) source · retrieved
  3. After RIPE NCC delegated statistics 2020-12-09 (produced 2020-12-09T22:59:00+00:00), after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.4.0) current
2020-12-09 APNIC Transfer log Inter-RIR transfer into APNIC Confirmed
Transfer log
Transfer: ORG-PDAC1-RIPE (RIPE NCC) to Kaopu Cloud HK Limited (APNIC)
From
ORG-PDAC1-RIPE RIPE NCC
To
Kaopu Cloud HK Limited APNIC
Same transfer
Also a change at the RIPE NCC, the sending registry: RIPE NCC, 2020-12-09. 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 ORG-PDAC1-RIPE (RIPE NCC) to Kaopu Cloud HK Limited (APNIC) on 2020-12-09 05:29 UTC: it came to APNIC from the RIPE NCC. 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 2020-12-09 05:29 UTC, ORG-PDAC1-RIPE (RIPE NCC) to Kaopu Cloud HK Limited (APNIC); resources moved: 194.26.72.0/22 source · retrieved
  2. Before APNIC delegated statistics 2020-12-09, before the change: not listed source · retrieved
  3. After APNIC delegated statistics 2020-12-10, after the change: allocated (dated 2018-07-24) 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
2018-07-24 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
194.26.72.0/22 available on 2018-07-23, allocated on 2018-07-24
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2018-07-23 and allocated (dated 2018-07-24) on 2018-07-24. The tracker saw this range removed from registration on 2014-12-05 (194.26.72.0/22), so it appears to have been issued again from the RIPE NCC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 194.26.72.0/22 available on 2018-07-23, allocated on 2018-07-24 source · retrieved
  2. Before RIPE NCC delegated statistics 2018-07-23 (produced 2018-07-23T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2018-07-24 (produced 2018-07-24T21:59:59+00:00), after the change: allocated (dated 2018-07-24) 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
2014-12-05 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
194.26.72.0/22 assigned on 2014-12-04, reserved on 2014-12-05
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2015-06-03. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 1995-04-10) on 2014-12-04 and reserved on 2014-12-05. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2015-06-03. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 194.26.72.0/22 assigned on 2014-12-04, reserved on 2014-12-05 source · retrieved
  2. Before RIPE NCC delegated statistics 2014-12-04 (produced 2014-12-04T22:59:59+00:00), before the change: assigned (dated 1995-04-10) source · retrieved
  3. After RIPE NCC delegated statistics 2014-12-05 (produced 2014-12-05T22:59:59+00:00), 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

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer194.26.72.0/22 Pishgaman Dadeh Afzar Company Ltd. RIPE NCC(no name given) APNIC
APNICResource transfer194.26.72.0/22 ORG-PDAC1-RIPE RIPE NCCKaopu Cloud HK Limited 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/194.26.72.0-194.26.75.255.json