Transferred into RIPE NCC administration; not a new issuance
Timeline (1)
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.
2019-12-03RIPE NCCTransfer logInter-RIR transfer into the RIPE NCCConfirmed
Transfer log
Transfer: (no name) (APNIC) to UMPIRE ASSOCIATES LTD (RIPE NCC)
From
(no name given) APNIC
To
UMPIRE ASSOCIATES LTD RIPE NCC
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2019-12-04. 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 UMPIRE ASSOCIATES LTD (RIPE NCC) on 2019-12-03 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 2019-12-03 19:00 UTC, (no name) (APNIC) to UMPIRE ASSOCIATES LTD (RIPE NCC); resources moved: 203.29.54.0/23source · retrieved
BeforeRIPE NCC delegated statistics 2019-12-02 (produced 2019-12-02T22:59:59+00:00), before the change: not listedsource · retrieved
AfterRIPE NCC delegated statistics 2019-12-03 (produced 2019-12-03T22:59:59+00:00), after the change: allocated (dated 1996-07-09)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
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.