Transferred out of APNIC administration; not offered to APNIC 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.
2025-01-22APNICTransfer logInter-RIR transfer out of APNICConfirmed
Transfer log
Transfer: NetMax Technologies Pvt. Ltd. (APNIC) to ORG-ZHL2-RIPE (RIPE NCC)
Transferred out of APNIC administration; not offered to APNIC applicants
APNIC's transfer log records a transfer from NetMax Technologies Pvt. Ltd. (APNIC) to ORG-ZHL2-RIPE (RIPE NCC) on 2025-01-21 21:38 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,
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-01-21 21:38 UTC, NetMax Technologies Pvt. Ltd. (APNIC) to ORG-ZHL2-RIPE (RIPE NCC); resources moved: 202.50.52.0/22source · retrieved
BeforeAPNIC delegated statistics 2025-01-22, before the change: allocated (dated 2011-04-07)source · retrieved
AfterAPNIC delegated statistics 2025-01-23, after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of APNIC, confirmed (classifier 1.4.0) current
2025-01-21RIPE NCCTransfer logInter-RIR transfer into the RIPE NCCConfirmed
Transfer log
Transfer: (no name) (APNIC) to Zappie Host LLC (RIPE NCC)
From
(no name given) APNIC
To
Zappie Host LLC RIPE NCC
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2025-01-22. 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 Zappie Host LLC (RIPE NCC) on 2025-01-21 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,
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-01-21 19:00 UTC, (no name) (APNIC) to Zappie Host LLC (RIPE NCC); resources moved: 202.50.52.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2025-01-20 (produced 2025-01-20T22:59:59+00:00), before the change: not listedsource · retrieved
AfterRIPE NCC delegated statistics 2025-01-21 (produced 2025-01-21T22:59:59+00:00), after the change: allocated (dated 2011-04-07)source · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.0)
: Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.1)
: Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.2)
: Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.4.0) current
2011-04-07APNIC+ RegisteredApparent reissuance of previously removed resourceStrong inference
Statistics
202.50.52.0/22 available on 2011-04-07, allocated on 2011-04-08
Inventory
Likely issued from APNIC-controlled inventory
No transfer record matches. APNIC's statistics show it available on 2011-04-07 and allocated (dated 2011-04-07) on 2011-04-08. The tracker saw this range removed from registration on 2010-12-21 (202.50.52.0/22), so it appears to have been issued again from APNIC's pool.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 202.50.52.0/22 available on 2011-04-07, allocated on 2011-04-08source · retrieved
BeforeAPNIC delegated statistics 2011-04-07, before the change: availablesource · retrieved
AfterAPNIC delegated statistics 2011-04-08, after the change: allocated (dated 2011-04-07)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current
2010-12-21APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Observed only
Statistics
202.50.52.0/22 allocated on 2010-12-21, not listed on 2010-12-22
Inventory
Possible future reissue candidate after hold
Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 1995-04-21) on 2010-12-21 and not listed on 2010-12-22. Being gone from APNIC's statistics entirely can also mean it moved to another registry. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, and its statistics show a steady one (a year) only for removals from 2014-07-01 on; this one came earlier, so the tracker gives no estimate. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 202.50.52.0/22 allocated on 2010-12-21, not listed on 2010-12-22source · retrieved
BeforeAPNIC delegated statistics 2010-12-21, before the change: allocated (dated 1995-04-21)source · retrieved
AfterAPNIC delegated statistics 2010-12-22, after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.4.0) current
Transfer records (2)
Date (UTC)
Log
Type
Range moved
From
To
APNIC
Resource transfer
202.50.52.0/22
NetMax Technologies Pvt. Ltd. APNIC
ORG-ZHL2-RIPE RIPE NCC
RIPE NCC
Resource transfer
202.50.52.0/22
(no name given) APNIC
Zappie Host LLC 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.