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.
Transfer: Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. (RIPE NCC) to DGN TEKNOLOJI A.S. (RIPE NCC)
From
Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. RIPE NCC
To
DGN TEKNOLOJI A.S. RIPE NCC
Piece of
2.56.60.0/22: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. (RIPE NCC) to DGN TEKNOLOJI A.S. (RIPE NCC) on 2025-01-02 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-01-02 19:00 UTC, Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. (RIPE NCC) to DGN TEKNOLOJI A.S. (RIPE NCC); resources moved: 2.56.63.0/24source · retrieved
BeforeRIPE NCC delegated statistics 2025-01-01 (produced 2025-01-01T22:59:59+00:00), before the change: allocated (dated 2019-03-13)source · retrieved
AfterRIPE NCC delegated statistics 2025-01-02 (produced 2025-01-02T22:59:59+00:00), after the change: allocated (dated 2019-03-13)source · retrieved
Classification history for this change (4 versions)
Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. RIPE NCC
DGN TEKNOLOJI A.S. RIPE NCC
RIPE NCC
Resource transfer
2.56.60.0/22
Hakan Ulug RIPE NCC
Yesilbir Bilisim Teknolojileri Bilgisayar Yayincilik Sanayi ve Ticaret Ltd. Sti. 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.