rirtracker

IPv4 range · 512 addresses

91.198.170.0/23

Now

RIPE NCC statistics
Allocated (dated 2019-10-03) (NL), in the latest file
Registry
RIPE NCC
Holder
Esmero Holding B.V.
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2023-06-26 (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-06-26 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: T. Hoogerheide Holding B.V. (RIPE NCC) to Esmero Holding B.V. (RIPE NCC)
From
T. Hoogerheide Holding B.V. RIPE NCC
To
Esmero Holding B.V. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from T. Hoogerheide Holding B.V. (RIPE NCC) to Esmero Holding B.V. (RIPE NCC) on 2023-06-26 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-06-26 19:00 UTC, T. Hoogerheide Holding B.V. (RIPE NCC) to Esmero Holding B.V. (RIPE NCC); resources moved: 91.198.170.0/23 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-06-25 (produced 2023-06-25T21:59:59+00:00), before the change: allocated (dated 2019-10-03) source · retrieved
  3. After RIPE NCC delegated statistics 2023-06-26 (produced 2023-06-26T21:59:59+00:00), after the change: allocated (dated 2019-10-03) 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-10-03 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
91.198.170.0/23 available on 2019-10-02, allocated on 2019-10-03
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2019-10-02 and allocated (dated 2019-10-03) on 2019-10-03. The tracker saw this range removed from registration on 2016-11-17 (91.198.171.0/24), so it appears to have been issued again from the RIPE NCC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 91.198.170.0/23 available on 2019-10-02, allocated on 2019-10-03 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-10-02 (produced 2019-10-02T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2019-10-03 (produced 2019-10-03T21:59:59+00:00), after the change: allocated (dated 2019-10-03) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2016-11-17RIPE NCC91.198.171.0/24− DeregisteredRemoved
2013-11-06RIPE NCC91.198.170.0/24ReleasedHold released
2012-11-06RIPE NCC91.198.170.0/24− DeregisteredRemoved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer91.198.170.0/23 T. Hoogerheide Holding B.V. RIPE NCCEsmero Holding B.V. 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/91.198.170.0-91.198.171.255.json