Transferred out of ARIN administration; not offered to ARIN applicants
Timeline (7)
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-05-06ARINNot in ARIN-IssuedInter-RIR transfer out of ARINConfirmed
Transferred out of ARIN administration; not offered to ARIN applicants
ARIN's transfer log records a transfer from Alpha InfoLab Inc (ARIN) to code200 UAB (RIPE NCC) on 2025-05-06 14:09 UTC: it left ARIN for the RIPE NCC. 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,
StatisticsNot listed in ARIN-Issued; found by comparing ARIN's daily statistics: 139.5.20.0/22 allocated on 2025-05-06, not listed on 2025-05-07source · retrieved
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-05-06 14:09 UTC, Alpha InfoLab Inc (ARIN) to code200 UAB (RIPE NCC); resources moved: 139.5.20.0/22source · retrieved
BeforeARIN delegated statistics 2025-05-05 (produced 2025-05-05T13:01:09+00:00), before the report: allocated (dated 2022-03-08)source · retrieved
AfterARIN delegated statistics 2025-05-07 (produced 2025-05-07T13:01:09+00:00), after the report: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.4.0) current
2025-05-06RIPE NCCTransfer logInter-RIR transfer into the RIPE NCCConfirmed
Transfer log
Transfer: (no name) (ARIN) to UAB code200 (RIPE NCC)
From
(no name given) ARIN
To
UAB code200 RIPE NCC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2025-05-06. 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 (ARIN) to UAB code200 (RIPE NCC) on 2025-05-06 19:00 UTC: it came to the RIPE NCC from ARIN. 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-05-06 19:00 UTC, (no name) (ARIN) to UAB code200 (RIPE NCC); resources moved: 139.5.20.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2025-05-05 (produced 2025-05-05T21:59:59+00:00), before the change: not listedsource · retrieved
AfterRIPE NCC delegated statistics 2025-05-06 (produced 2025-05-06T21:59:59+00:00), after the change: allocated (dated 2022-03-08)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
2022-03-09APNICTransfer logInter-RIR transfer out of APNICConfirmed
Transfer log
Transfer: NIXI/DATAFORCE (APNIC) to AI-1720 (ARIN)
Transferred out of APNIC administration; not offered to APNIC applicants
APNIC's transfer log records a transfer from NIXI/DATAFORCE (APNIC) to AI-1720 (ARIN) on 2022-03-08 22:25 UTC: it left APNIC for ARIN. 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 2022-03-08 22:25 UTC, NIXI/DATAFORCE (APNIC) to AI-1720 (ARIN); resources moved: 103.207.44.0/22, 139.5.20.0/22source · retrieved
BeforeAPNIC delegated statistics 2022-03-09, before the change: allocated (dated 2016-02-29)source · retrieved
AfterAPNIC delegated statistics 2022-03-10, 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
2022-03-08ARIN+ AddInter-RIR transfer into ARINConfirmed
ARIN-Issued
Add 139.5.20.0-139.5.23.255
From
Dataforce Network Private Limited APNIC
To
Alpha InfoLab Inc ARIN
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2022-03-09. Lists that cover every registry show it there.
Inventory
Transferred into ARIN administration; not a new issuance
ARIN's transfer log records a transfer from Dataforce Network Private Limited (APNIC) to Alpha InfoLab Inc (ARIN) on 2022-03-08 21:32 UTC: it came to ARIN from APNIC. It was already issued by another registry, so this is not a new issuance.
Evidence (4) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2022-03-08: "Add 139.5.20.0-139.5.23.255"source · retrieved
Transfer logTransfer log: RESOURCE_TRANSFER on 2022-03-08 21:32 UTC, Dataforce Network Private Limited (APNIC) to Alpha InfoLab Inc (ARIN); resources moved: 139.5.20.0/22source · retrieved
BeforeARIN delegated statistics 2022-03-07 (produced 2022-03-07T14:00:10+00:00), before the report: not listedsource · retrieved
AfterARIN delegated statistics 2022-03-09 (produced 2022-03-09T14:00:11+00:00), after the report: allocated (dated 2022-03-08)source · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer into ARIN, confirmed (classifier 1.3.0)
: Inter-RIR transfer into ARIN, confirmed (classifier 1.3.1)
: Inter-RIR transfer into ARIN, confirmed (classifier 1.3.2)
: Inter-RIR transfer into ARIN, confirmed (classifier 1.4.0) current
2020-10-26APNIC+ RegisteredRestored to the same holderStrong inference
Statistics
139.5.20.0/22 reserved on 2020-10-26, allocated on 2020-10-27
Inventory
No effect on APNIC applicant inventory
No transfer record matches. APNIC's statistics show it reserved on 2020-10-26 and allocated (dated 2016-02-29) on 2020-10-27. The tracker saw it removed from registration on 2020-07-15 (103 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 139.5.20.0/22 reserved on 2020-10-26, allocated on 2020-10-27source · retrieved
BeforeAPNIC delegated statistics 2020-10-26, before the change: reservedsource · retrieved
AfterAPNIC delegated statistics 2020-10-27, after the change: allocated (dated 2016-02-29)source · retrieved
Classification history for this change (4 versions)
: Restored to the same holder, strong inference (classifier 1.3.0)
: Restored to the same holder, strong inference (classifier 1.3.1)
: Restored to the same holder, strong inference (classifier 1.3.2)
: Restored to the same holder, strong inference (classifier 1.4.0) current
2020-07-15APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
139.5.20.0/22 allocated on 2020-07-15, reserved on 2020-07-16
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2021-07-15. 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 2016-02-29) on 2020-07-15 and reserved on 2020-07-16. 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 2021-07-15. That is what APNIC has done, not a rule it states. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 139.5.20.0/22 allocated on 2020-07-15, reserved on 2020-07-16source · retrieved
BeforeAPNIC delegated statistics 2020-07-15, before the change: allocated (dated 2016-02-29)source · retrieved
AfterAPNIC delegated statistics 2020-07-16, after the change: reservedsource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2016-02-29APNIC+ RegisteredApparent new issuanceStrong inference
Statistics
139.5.20.0/22 available on 2016-02-29, allocated on 2016-03-01
Inventory
Likely issued from APNIC-controlled inventory
No transfer record matches. APNIC's statistics show it available on 2016-02-29 and allocated (dated 2016-02-29) on 2016-03-01. It moved from APNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by APNIC.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 139.5.20.0/22 available on 2016-02-29, allocated on 2016-03-01source · retrieved
BeforeAPNIC delegated statistics 2016-02-29, before the change: availablesource · retrieved
AfterAPNIC delegated statistics 2016-03-01, after the change: allocated (dated 2016-02-29)source · retrieved
Classification history for this change (4 versions)
: Apparent new issuance, strong inference (classifier 1.3.0)
: Apparent new issuance, strong inference (classifier 1.3.1)
: Apparent new issuance, strong inference (classifier 1.3.2)
: Apparent new issuance, strong inference (classifier 1.4.0) current
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.