rirtracker

IPv4 range · 512 addresses

31.14.46.0/23

Now

RIPE NCC statistics
Allocated (dated 2011-04-18) (DE), in the latest file
Registry
RIPE NCC
Holder
Bradler & Krantz GmbH & Co. KG
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2019-11-15 (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.

2019-11-15 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Megaspace Internet Services GmbH (RIPE NCC) to Bradler & Krantz GmbH & Co. KG (RIPE NCC)
From
Megaspace Internet Services GmbH RIPE NCC
To
Bradler & Krantz GmbH & Co. KG RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Megaspace Internet Services GmbH (RIPE NCC) to Bradler & Krantz GmbH & Co. KG (RIPE NCC) on 2019-11-15 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-11-15 19:00 UTC, Megaspace Internet Services GmbH (RIPE NCC) to Bradler & Krantz GmbH & Co. KG (RIPE NCC); resources moved: 31.14.46.0/23 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-11-14 (produced 2019-11-14T22:59:59+00:00), before the change: allocated (dated 2011-04-18) source · retrieved
  3. After RIPE NCC delegated statistics 2019-11-15 (produced 2019-11-15T22:59:59+00:00), after the change: allocated (dated 2011-04-18) 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
2015-05-28 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Jump Management SRL (RIPE NCC) to Megaspace Internet Services GmbH (RIPE NCC)
From
Jump Management SRL RIPE NCC
To
Megaspace Internet Services GmbH RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Jump Management SRL (RIPE NCC) to Megaspace Internet Services GmbH (RIPE NCC) on 2015-05-28 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 2015-05-28 19:00 UTC, Jump Management SRL (RIPE NCC) to Megaspace Internet Services GmbH (RIPE NCC); resources moved: 31.14.46.0/23 source · retrieved
  2. Before RIPE NCC delegated statistics 2015-05-27 (produced 2015-05-27T21:59:59+00:00), before the change: allocated (dated 2011-04-18) source · retrieved
  3. After RIPE NCC delegated statistics 2015-05-28 (produced 2015-05-28T21:59:59+00:00), after the change: allocated (dated 2011-04-18) 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
2011-04-19RIPE NCC31.14.0.0/16+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer31.14.46.0/23 Megaspace Internet Services GmbH RIPE NCCBradler & Krantz GmbH & Co. KG RIPE NCC
RIPE NCCResource transfer31.14.46.0/23 Jump Management SRL RIPE NCCMegaspace Internet Services 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

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/31.14.46.0-31.14.47.255.json