Transferred into RIPE NCC administration; not a new issuance
Timeline (3)
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-02-19RIPE NCCTransfer logInter-RIR transfer into the RIPE NCCConfirmed
Transfer log
Transfer: (no name) (LACNIC) to HLC Cloud DMCC (RIPE NCC)
From
(no name given) LACNIC
To
HLC Cloud DMCC RIPE NCC
Same transfer
Also a change at LACNIC, the sending registry: LACNIC, 2025-02-19. 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 (LACNIC) to HLC Cloud DMCC (RIPE NCC) on 2025-02-19 19:00 UTC: it came to the RIPE NCC from LACNIC. 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-02-19 19:00 UTC, (no name) (LACNIC) to HLC Cloud DMCC (RIPE NCC); resources moved: 45.177.236.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2025-02-18 (produced 2025-02-18T22:59:59+00:00), before the change: not listedsource · retrieved
AfterRIPE NCC delegated statistics 2025-02-19 (produced 2025-02-19T22:59:59+00:00), after the change: allocated (dated 2019-06-04)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
2025-02-19LACNICTransfer logInter-RIR transfer out of LACNICConfirmed
Transfer log
Transfer: ULTIMA MILLA S.A (LACNIC) to HLC Cloud DMCC (RIPE NCC)
Transferred out of LACNIC administration; not offered to LACNIC applicants
LACNIC's transfer log records a transfer from ULTIMA MILLA S.A (LACNIC) to HLC Cloud DMCC (RIPE NCC) on 2025-02-19 13:00 UTC: it left LACNIC for the RIPE NCC. It is not a new allocation and is not offered to LACNIC applicants.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-02-19 13:00 UTC, ULTIMA MILLA S.A (LACNIC) to HLC Cloud DMCC (RIPE NCC); resources moved: 45.177.236.0/22source · retrieved
BeforeLACNIC delegated statistics 2025-02-18, before the change: allocated (dated 2019-06-04)source · retrieved
AfterLACNIC delegated statistics 2025-02-19, after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of LACNIC, confirmed (classifier 1.4.0) current
2019-06-04LACNIC+ RegisteredApparent reissuance of previously removed resourceStrong inference
Statistics
45.177.236.0/22 reserved on 2019-06-03, allocated on 2019-06-04
Inventory
Likely issued from LACNIC-controlled inventory
No transfer record matches. LACNIC's statistics show it reserved on 2019-06-03 and allocated (dated 2019-06-04) on 2019-06-04. The tracker saw this range released from hold on 2017-04-05 (45.160.0.0/11), so it appears to have been issued again from LACNIC's pool.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing LACNIC's daily statistics: 45.177.236.0/22 reserved on 2019-06-03, allocated on 2019-06-04source · retrieved
BeforeLACNIC delegated statistics 2019-06-03, before the change: reservedsource · retrieved
AfterLACNIC delegated statistics 2019-06-04, after the change: allocated (dated 2019-06-04)source · retrieved
Classification history for this change (4 versions)
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.