rirtracker

IPv4 range · 16,384 addresses

208.117.0.0/18

Now

ARIN statistics
Allocated (dated 2010-08-19), allocated (dated 2022-04-13) (US), in the latest file
Registry
ARIN
Holder
Steadfast
From
ARIN's latest statistics and the latest transfer record

Latest change

Transfer log Merger/acquisition or reorganization

Reported
2016-08-11 (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.

2016-08-11 ARIN Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: Steadfast Networks (ARIN) to Steadfast (ARIN)
From
Steadfast Networks ARIN
To
Steadfast ARIN
Inventory
No effect on ARIN applicant inventory

ARIN's transfer log records a merger, acquisition or reorganization from Steadfast Networks (ARIN) to Steadfast (ARIN) on 2016-08-11 14:16 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 2016-08-11 14:16 UTC, Steadfast Networks (ARIN) to Steadfast (ARIN); resources moved: 208.117.0.0/18 source · retrieved
  2. Before ARIN delegated statistics 2016-08-10 (produced 2016-08-10T05:09:35+00:00), before the report: allocated (dated 2010-08-19) source · retrieved
  3. After ARIN delegated statistics 2016-08-12 (produced 2016-08-12T05:10:38+00:00), after the report: allocated (dated 2010-08-19) source · retrieved
2010-08-19 ARIN + Add Apparent reissuance of previously removed resource Strong inference
ARIN-Issued
Add 208.117.0.0-208.117.63.255
Inventory
Likely issued from ARIN-controlled inventory

No transfer record matches. ARIN's statistics show it not issued on 2010-08-18 and allocated (dated 2010-08-19) on 2010-08-20. (Until 2013-03-05, ARIN's statistics list only what's issued.) The tracker saw this range released from hold on 2010-07-29 (208.117.0.0-208.117.95.255), so it appears to have been issued again from ARIN's pool.

Evidence (3) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2010-08-19: "Add 208.117.0.0-208.117.63.255" source · retrieved
  2. Before ARIN delegated statistics 2010-08-18, before the report: not issued source · retrieved
  3. After ARIN delegated statistics 2010-08-20, after the report: allocated (dated 2010-08-19) 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

Sold in pieces

1 piece of this block transferred since 2008-12-01, 25% of it so far.

DatePieceWhat happenedFromTo
2022-04-13 208.117.48.0/20Intra-ARIN transfer Steadfast ARINTwilio SendGrid ARIN

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2022-04-13ARIN208.117.48.0/20+ AddIntra-ARIN transfer
2010-07-29ARIN208.117.0.0 - 208.117.95.255− RemoveUnresolved
2009-07-27ARIN208.117.0.0 - 208.117.95.255Not in ARIN-IssuedRemoved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
ARINResource transfer208.117.48.0/20 Steadfast ARINTwilio SendGrid ARIN
ARINMerger acquisition208.117.0.0/18 Steadfast Networks ARINSteadfast 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.117.0.0-208.117.63.255.json