Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants
Timeline (2)
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-08-14RIPE NCCTransfer logInter-RIR transfer out of the RIPE NCCConfirmed
Transfer log
Transfer: Balfour Beatty PLC (RIPE NCC) to (no name) (APNIC)
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants
The RIPE NCC's transfer log records a transfer from Balfour Beatty PLC (RIPE NCC) to an unnamed organization (APNIC) on 2019-08-14 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,
Transfer logTransfer log: RESOURCE_TRANSFER on 2019-08-14 19:00 UTC, Balfour Beatty PLC (RIPE NCC) to (no name) (APNIC); resources moved: 138.248.64.0/18source · retrieved
BeforeRIPE NCC delegated statistics 2019-08-13 (produced 2019-08-13T21:59:59+00:00), before the change: assigned (dated 1993-09-01)source · retrieved
AfterRIPE NCC delegated statistics 2019-08-14 (produced 2019-08-14T21:59:59+00:00), after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.4.0) current
2019-08-14APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: ORG-BB232-RIPE (RIPE NCC) to Japan Network Information Center/KK-NET (APNIC)
From
ORG-BB232-RIPE RIPE NCC
To
Japan Network Information Center/KK-NET APNIC
Same transfer
Also a change at the RIPE NCC, the sending registry: RIPE NCC, 2019-08-14. 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-BB232-RIPE (RIPE NCC) to Japan Network Information Center/KK-NET (APNIC) on 2019-08-14 05:44 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,
Transfer logTransfer log: RESOURCE_TRANSFER on 2019-08-14 05:44 UTC, ORG-BB232-RIPE (RIPE NCC) to Japan Network Information Center/KK-NET (APNIC); resources moved: 138.248.64.0/18source · retrieved
BeforeAPNIC delegated statistics 2019-08-14, before the change: not listedsource · retrieved
AfterAPNIC delegated statistics 2019-08-15, after the change: allocated (dated 1993-09-01)source · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.0)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.1)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.2)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.4.0) current
Transfer records (2)
Date (UTC)
Log
Type
Range moved
From
To
RIPE NCC
Resource transfer
138.248.64.0/18
Balfour Beatty PLC RIPE NCC
(no name given) APNIC
APNIC
Resource transfer
138.248.64.0/18
ORG-BB232-RIPE RIPE NCC
Japan Network Information Center/KK-NET 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.