rirtracker

IPv4 range · 8,192 addresses

87.251.0.0/19

Now

RIPE NCC statistics
Allocated (dated 2005-09-08) (DE, GB, TR, US), in the latest file
Registry
RIPE NCC
Holder
VERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2020-06-08 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

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.

2020-06-08 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Ispro Iletisium Hiz Ve Yazilim San Tic A S (RIPE NCC) to VERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI (RIPE NCC)
From
Ispro Iletisium Hiz Ve Yazilim San Tic A S RIPE NCC
To
VERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Ispro Iletisium Hiz Ve Yazilim San Tic A S (RIPE NCC) to VERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI (RIPE NCC) on 2020-06-08 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2020-06-08 19:00 UTC, Ispro Iletisium Hiz Ve Yazilim San Tic A S (RIPE NCC) to VERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI (RIPE NCC); resources moved: 87.251.0.0/19 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-06-07 (produced 2020-06-07T21:59:59+00:00), before the change: allocated (dated 2005-09-08) source · retrieved
  3. After RIPE NCC delegated statistics 2020-06-08 (produced 2020-06-08T21:59:59+00:00), after the change: allocated (dated 2005-09-08) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current

Sold in pieces

2 pieces of this block transferred since 2010-04-23, 28% of it so far.

DatePieceWhat happenedFromTo
2023-08-02 87.251.24.0/21Intra-RIPE NCC transfer Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCSpaceX Services, Inc. RIPE NCC
2024-02-02 87.251.23.0/24Intra-RIPE NCC transfer Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCLC Waikiki Magazacilik Hiz. Tic. A.S. RIPE NCC

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2025-01-07RIPE NCC87.251.16.0/22Transfer logIntra-RIPE NCC transfer
2024-12-09RIPE NCC87.251.0.0/20Transfer logIntra-RIPE NCC transfer
2024-11-05RIPE NCC87.251.20.0/23Transfer logIntra-RIPE NCC transfer
2024-02-02RIPE NCC87.251.23.0/24Transfer logIntra-RIPE NCC transfer
2023-08-02RIPE NCC87.251.24.0/21Transfer logIntra-RIPE NCC transfer

Transfer records (6)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer87.251.16.0/22 Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCAce Data Centers II, LLC RIPE NCC
RIPE NCCResource transfer87.251.0.0/20 Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCPlaytech Software Ltd RIPE NCC
RIPE NCCResource transfer87.251.20.0/23 Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCOC Payment GmbH RIPE NCC
RIPE NCCResource transfer87.251.23.0/24 Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCLC Waikiki Magazacilik Hiz. Tic. A.S. RIPE NCC
RIPE NCCResource transfer87.251.24.0/21 Veriteknik Bilisim Basin Ve Yayin Limited Sirketi RIPE NCCSpaceX Services, Inc. RIPE NCC
RIPE NCCResource transfer87.251.0.0/19 Ispro Iletisium Hiz Ve Yazilim San Tic A S RIPE NCCVERITEKNIK BILISIM BASIN VE YAYIN LIMITED SIRKETI 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.

This page as data: ip/87.251.0.0-87.251.31.255.json