rirtracker

IPv4 range · 256 addresses

208.89.70.0/24

Now

ARIN statistics
Allocated (dated 2008-04-11) (US), in the latest file
Registry
ARIN
Holder
InComm
From
ARIN's latest statistics and the latest transfer record

Latest change

Transfer log Merger/acquisition or reorganization

Reported
2018-04-02 (ARIN)
Confidence
Confirmed
Inventory
No effect on ARIN applicant inventory

Timeline (1)

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.

2018-04-02 ARIN Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: Incomm (ARIN) to InComm (ARIN)
From
Incomm ARIN
To
InComm ARIN
Piece of
208.89.64.0/21: the rest of the block stayed with the seller
Inventory
No effect on ARIN applicant inventory

ARIN's transfer log records a merger, acquisition or reorganization from Incomm (ARIN) to InComm (ARIN) on 2018-04-02 13:54 UTC. The registration changed hands; it is not a new allocation from ARIN. ARIN-Issued and ARIN's statistics don't show this change; only the transfer log records it.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: MERGER_ACQUISITION on 2018-04-02 13:54 UTC, Incomm (ARIN) to InComm (ARIN); resources moved: 208.89.70.0/24 source · retrieved
  2. Before ARIN delegated statistics 2018-04-01 (produced 2018-04-01T05:11:30+00:00), before the report: allocated (dated 2008-04-11) source · retrieved
  3. After ARIN delegated statistics 2018-04-03 (produced 2018-04-03T05:11:31+00:00), after the report: assigned (dated 2008-04-11) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
ARINMerger acquisition208.89.70.0/24 Incomm ARINInComm ARIN

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/208.89.70.0-208.89.70.255.json