Transferred out of APNIC administration; not offered to APNIC 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.
2023-10-24APNICTransfer logInter-RIR transfer out of APNICConfirmed
Transfer log
Transfer: RDU98.5FM Limited (APNIC) to ORG-DCTD1-RIPE (RIPE NCC)
Transferred out of APNIC administration; not offered to APNIC applicants
APNIC's transfer log records a transfer from RDU98.5FM Limited (APNIC) to ORG-DCTD1-RIPE (RIPE NCC) on 2023-10-23 22:12 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 2023-10-23 22:12 UTC, RDU98.5FM Limited (APNIC) to ORG-DCTD1-RIPE (RIPE NCC); resources moved: 202.37.103.0/24source · retrieved
BeforeAPNIC delegated statistics 2023-10-24, before the change: assigned (dated 1995-10-25)source · retrieved
AfterAPNIC delegated statistics 2023-10-25, 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
2023-10-23RIPE NCCTransfer logInter-RIR transfer into the RIPE NCCConfirmed
Transfer log
Transfer: (no name) (APNIC) to Data Cloud Technology d.o.o Kragujevac (RIPE NCC)
From
(no name given) APNIC
To
Data Cloud Technology d.o.o Kragujevac RIPE NCC
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2023-10-24. 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 Data Cloud Technology d.o.o Kragujevac (RIPE NCC) on 2023-10-23 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 2023-10-23 19:00 UTC, (no name) (APNIC) to Data Cloud Technology d.o.o Kragujevac (RIPE NCC); resources moved: 202.37.103.0/24source · retrieved
BeforeRIPE NCC delegated statistics 2023-10-22 (produced 2023-10-22T21:59:59+00:00), before the change: not listedsource · retrieved
AfterRIPE NCC delegated statistics 2023-10-23 (produced 2023-10-23T21:59:59+00:00), after the change: assigned (dated 1995-10-25)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
Transfer records (2)
Date (UTC)
Log
Type
Range moved
From
To
APNIC
Resource transfer
202.37.103.0/24
RDU98.5FM Limited APNIC
ORG-DCTD1-RIPE RIPE NCC
RIPE NCC
Resource transfer
202.37.103.0/24
(no name given) APNIC
Data Cloud Technology d.o.o Kragujevac 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.