rirtracker

IPv4 range · 2,048 addresses

66.9.32.0/21

Now

ARIN statistics
Allocated (dated 2023-11-21) (US), in the latest file
Registry
ARIN
Holder
Midcontinent Communications
From
ARIN's latest statistics and the latest transfer record

Latest change

Transfer log Merger/acquisition or reorganization

Reported
2025-12-10 (ARIN)
Confidence
Confirmed
Inventory
No effect on ARIN 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.

2025-12-10 ARIN Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: Savage Communications Inc. (ARIN) to Midcontinent Communications (ARIN)
From
Savage Communications Inc. ARIN
To
Midcontinent Communications ARIN
Inventory
No effect on ARIN applicant inventory

ARIN's transfer log records a merger, acquisition or reorganization from Savage Communications Inc. (ARIN) to Midcontinent Communications (ARIN) on 2025-12-10 15:46 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 2025-12-10 15:46 UTC, Savage Communications Inc. (ARIN) to Midcontinent Communications (ARIN); resources moved: 66.9.32.0/21 source · retrieved
  2. Before ARIN delegated statistics 2025-12-09 (produced 2025-12-09T14:00:47+00:00), before the report: allocated (dated 2023-11-21) source · retrieved
  3. After ARIN delegated statistics 2025-12-11 (produced 2025-12-11T14:00:47+00:00), after the report: allocated (dated 2023-11-21) source · retrieved
2023-11-21 ARIN + Add Intra-ARIN transfer Confirmed
ARIN-Issued
Add 66.9.32.0-66.9.39.255
From
M2ngage Telecommunications II Corp. ARIN
To
Savage Communications Inc. ARIN
Inventory
No effect on ARIN applicant inventory

ARIN's transfer log records a transfer from M2ngage Telecommunications II Corp. (ARIN) to Savage Communications Inc. (ARIN) on 2023-11-21 15:52 UTC. ARIN-Issued lists it as "Add" because the registration changed hands; it is not a new allocation from ARIN.

Evidence (4) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2023-11-21: "Add 66.9.32.0-66.9.39.255" source · retrieved
  2. Transfer log Transfer log: RESOURCE_TRANSFER on 2023-11-21 15:52 UTC, M2ngage Telecommunications II Corp. (ARIN) to Savage Communications Inc. (ARIN); resources moved: 66.9.32.0/21 source · retrieved
  3. Before ARIN delegated statistics 2023-11-20 (produced 2023-11-20T14:00:34+00:00), before the report: allocated (dated 2000-09-12) source · retrieved
  4. After ARIN delegated statistics 2023-11-22 (produced 2023-11-22T14:00:34+00:00), after the report: allocated (dated 2023-11-21) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-ARIN transfer, confirmed (classifier 1.3.0)
  2. : Intra-ARIN transfer, confirmed (classifier 1.3.1)
  3. : Intra-ARIN transfer, confirmed (classifier 1.3.2)
  4. : Intra-ARIN transfer, confirmed (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2017-08-14ARIN66.9.0.0/16Transfer logMerger/acquisition

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
ARINMerger acquisition66.9.32.0/21 Savage Communications Inc. ARINMidcontinent Communications ARIN
ARINResource transfer66.9.32.0/21 M2ngage Telecommunications II Corp. ARINSavage Communications Inc. ARIN
ARINMerger acquisition66.9.0.0/16 Wave2Wave Communications, Inc ARINM2ngage Telecommunications II Corp. 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/66.9.32.0-66.9.39.255.json