rirtracker

IPv4 range · 256 addresses

185.136.207.0/24

Now

RIPE NCC statistics
Allocated (dated 2016-02-02) (AZ), in the latest file
Registry
RIPE NCC
Holder
A2Z Technologies CJSC
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2023-01-09 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

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-01-09 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Mehmet Uzunca (RIPE NCC) to A2Z Technologies CJSC (RIPE NCC)
From
Mehmet Uzunca RIPE NCC
To
A2Z Technologies CJSC RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Mehmet Uzunca (RIPE NCC) to A2Z Technologies CJSC (RIPE NCC) on 2023-01-09 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 2023-01-09 19:00 UTC, Mehmet Uzunca (RIPE NCC) to A2Z Technologies CJSC (RIPE NCC); resources moved: 185.136.207.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-01-08 (produced 2023-01-08T22:59:59+00:00), before the change: allocated (dated 2016-02-02) source · retrieved
  3. After RIPE NCC delegated statistics 2023-01-09 (produced 2023-01-09T22:59:59+00:00), after the change: allocated (dated 2016-02-02) 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
2019-03-27 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Okkes Uzunca trading as Fiberserver Internet Teknolojileri (RIPE NCC) to Mehmet Uzunca (RIPE NCC)
From
Okkes Uzunca trading as Fiberserver Internet Teknolojileri RIPE NCC
To
Mehmet Uzunca RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Okkes Uzunca trading as Fiberserver Internet Teknolojileri (RIPE NCC) to Mehmet Uzunca (RIPE NCC) on 2019-03-27 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 2019-03-27 19:00 UTC, Okkes Uzunca trading as Fiberserver Internet Teknolojileri (RIPE NCC) to Mehmet Uzunca (RIPE NCC); resources moved: 185.136.207.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-03-26 (produced 2019-03-26T22:59:59+00:00), before the change: allocated (dated 2016-02-02) source · retrieved
  3. After RIPE NCC delegated statistics 2019-03-27 (produced 2019-03-27T22:59:59+00:00), after the change: allocated (dated 2016-02-02) 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

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2016-02-02RIPE NCC185.136.204.0/22+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer185.136.207.0/24 Mehmet Uzunca RIPE NCCA2Z Technologies CJSC RIPE NCC
RIPE NCCResource transfer185.136.207.0/24 Okkes Uzunca trading as Fiberserver Internet Teknolojileri RIPE NCCMehmet Uzunca 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/185.136.207.0-185.136.207.255.json