rirtracker

IPv4 range · 16,384 addresses

88.211.192.0/18

Now

RIPE NCC statistics
Allocated (dated 2005-12-08) (NL), in the latest file
Registry
RIPE NCC
Holder
Servers.com B.V.
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2023-11-01 (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-11-01 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Centric Telecom Limited (RIPE NCC) to Servers.com B.V. (RIPE NCC)
From
Centric Telecom Limited RIPE NCC
To
Servers.com B.V. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Centric Telecom Limited (RIPE NCC) to Servers.com B.V. (RIPE NCC) on 2023-11-01 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-01 19:00 UTC, Centric Telecom Limited (RIPE NCC) to Servers.com B.V. (RIPE NCC); resources moved: 88.211.192.0/18 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-10-31 (produced 2023-10-31T22:59:59+00:00), before the change: allocated (dated 2005-12-08) source · retrieved
  3. After RIPE NCC delegated statistics 2023-11-01 (produced 2023-11-01T22:59:59+00:00), after the change: allocated (dated 2005-12-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
2021-08-16 RIPE NCC Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: IntelliSpace (UK) Ltd (RIPE NCC) to Centric Telecom Limited (RIPE NCC)
From
IntelliSpace (UK) Ltd RIPE NCC
To
Centric Telecom Limited RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a merger, acquisition or reorganization from IntelliSpace (UK) Ltd (RIPE NCC) to Centric Telecom Limited (RIPE NCC) on 2021-08-16 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: MERGER_ACQUISITION on 2021-08-16 19:00 UTC, IntelliSpace (UK) Ltd (RIPE NCC) to Centric Telecom Limited (RIPE NCC); resources moved: 88.211.192.0/18 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-08-15 (produced 2021-08-15T21:59:00+00:00), before the change: allocated (dated 2005-12-08) source · retrieved
  3. After RIPE NCC delegated statistics 2021-08-16 (produced 2021-08-16T21:59:00+00:00), after the change: allocated (dated 2005-12-08) source · retrieved
Classification history for this change (4 versions)
  1. : Merger/acquisition or reorganization, confirmed (classifier 1.3.0)
  2. : Merger/acquisition or reorganization, confirmed (classifier 1.3.1)
  3. : Merger/acquisition or reorganization, confirmed (classifier 1.3.2)
  4. : Merger/acquisition or reorganization, confirmed (classifier 1.4.0) current

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer88.211.192.0/18 Centric Telecom Limited RIPE NCCServers.com B.V. RIPE NCC
RIPE NCCMerger acquisition88.211.192.0/18 IntelliSpace (UK) Ltd RIPE NCCCentric Telecom Limited 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/88.211.192.0-88.211.255.255.json