rirtracker

IPv4 range · 256 addresses

217.114.35.0/24

Now

RIPE NCC statistics
Allocated (dated 2021-10-05) (CN), in the latest file
Registry
RIPE NCC
Holder
BSol-mnt
From
RDAP, looked up 2026-11-12 18:23 UTC

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-11-12 (RIPE NCC)
Confidence
Confirmed Provisional
Inventory
No effect on RIPE NCC applicant inventory

Timeline (5)

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.

2026-11-12 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed Provisional
Transfer log
Transfer: Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC)
From
Xiamen Jiufu Network Co., Ltd. RIPE NCC
To
BHS Solutions GmbH RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC) on 2026-11-12 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (2) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-11-12 19:00 UTC, Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC); resources moved: 217.114.35.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-11-11 (produced 2026-11-11T22:59:59+00:00), before the change: allocated (dated 2021-10-05) source · retrieved
2025-11-12 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC)
From
Xiamen Jiufu Network Co., Ltd. RIPE NCC
To
BHS Solutions GmbH RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC) on 2025-11-12 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 2025-11-12 19:00 UTC, Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC); resources moved: 217.114.35.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2025-11-11 (produced 2025-11-11T22:59:59+00:00), before the change: allocated (dated 2021-10-05) source · retrieved
  3. After RIPE NCC delegated statistics 2025-11-12 (produced 2025-11-12T22:59:59+00:00), after the change: allocated (dated 2021-10-05) 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
2024-11-14 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC)
From
Xiamen Jiufu Network Co., Ltd. RIPE NCC
To
BHS Solutions GmbH RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC) on 2024-11-14 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 2024-11-14 19:00 UTC, Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC); resources moved: 217.114.35.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-11-13 (produced 2024-11-13T22:59:59+00:00), before the change: allocated (dated 2021-10-05) source · retrieved
  3. After RIPE NCC delegated statistics 2024-11-14 (produced 2024-11-14T22:59:59+00:00), after the change: allocated (dated 2021-10-05) 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
2023-11-03 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC)
From
Xiamen Jiufu Network Co., Ltd. RIPE NCC
To
BHS Solutions GmbH RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC) on 2023-11-03 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-11-03 19:00 UTC, Xiamen Jiufu Network Co., Ltd. (RIPE NCC) to BHS Solutions GmbH (RIPE NCC); resources moved: 217.114.35.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-11-02 (produced 2023-11-02T22:59:59+00:00), before the change: allocated (dated 2021-10-05) source · retrieved
  3. After RIPE NCC delegated statistics 2023-11-03 (produced 2023-11-03T22:59:59+00:00), after the change: allocated (dated 2021-10-05) 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
2021-10-05 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
217.114.35.0/24 available on 2021-10-04, allocated on 2021-10-05
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2021-10-04 and allocated (dated 2021-10-05) on 2021-10-05. The tracker saw this range released from hold on 2020-02-10 (217.114.32.0/20), 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: 217.114.35.0/24 available on 2021-10-04, allocated on 2021-10-05 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-10-04 (produced 2021-10-04T21:59:00+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2021-10-05 (produced 2021-10-05T21:59:00+00:00), after the change: allocated (dated 2021-10-05) 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
2020-02-10RIPE NCC217.114.32.0/20ReleasedHold released
2019-08-14RIPE NCC217.114.32.0/20− DeregisteredRemoved

Transfer records (4)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer217.114.35.0/24 Xiamen Jiufu Network Co., Ltd. RIPE NCCBHS Solutions GmbH RIPE NCC
RIPE NCCResource transfer217.114.35.0/24 Xiamen Jiufu Network Co., Ltd. RIPE NCCBHS Solutions GmbH RIPE NCC
RIPE NCCResource transfer217.114.35.0/24 Xiamen Jiufu Network Co., Ltd. RIPE NCCBHS Solutions GmbH RIPE NCC
RIPE NCCResource transfer217.114.35.0/24 Xiamen Jiufu Network Co., Ltd. RIPE NCCBHS Solutions GmbH 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

Looked upWhyRegistryHandleOrganizationStatusLast changed
First seen RIPE NCC217.114.35.0 - 217.114.35.255BSol-mntactive2026-11-12

Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.

This page as data: ip/217.114.35.0-217.114.35.255.json