rirtracker

ASN

AS50139

Now

RIPE NCC statistics
Allocated (dated 2021-09-01) on 2026-10-09 (TR)
Registry
RIPE NCC
Holder
eva bilgi teknolojileri san ve tic ltd sti
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-04-07 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-04-07 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Enforus Bilgi Ve Operasyon Teknolojileri Anonim Sirketi (RIPE NCC) to eva bilgi teknolojileri san ve tic ltd sti (RIPE NCC)
From
Enforus Bilgi Ve Operasyon Teknolojileri Anonim Sirketi RIPE NCC
To
eva bilgi teknolojileri san ve tic ltd sti RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Enforus Bilgi Ve Operasyon Teknolojileri Anonim Sirketi (RIPE NCC) to eva bilgi teknolojileri san ve tic ltd sti (RIPE NCC) on 2026-04-07 19:00 UTC. The registration changed hands; it is not a new allocation from RIPE NCC.

Evidence (3) · classifier 1.1.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-04-07 19:00 UTC, Enforus Bilgi Ve Operasyon Teknolojileri Anonim Sirketi (RIPE NCC) to eva bilgi teknolojileri san ve tic ltd sti (RIPE NCC); resources moved: AS50139 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-04-06 (produced 2026-04-06T21:59:59+00:00), before the change: allocated (dated 2021-09-01) source · retrieved
  3. After RIPE NCC delegated statistics 2026-04-07 (produced 2026-04-07T21:59:59+00:00), after the change: allocated (dated 2021-09-01) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transferAS50139 Enforus Bilgi Ve Operasyon Teknolojileri Anonim Sirketi RIPE NCCeva bilgi teknolojileri san ve tic ltd sti RIPE NCC

Every record in the ARIN and RIPE NCC transfer logs that moved any part of this ASN (ARIN's go back to 2009, the RIPE NCC's to 2012). 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.

This page as data: asn/50139.json