rirtracker

IPv4 range · 4,096 addresses

216.250.96.0/20

Now

ARIN statistics
Allocated (dated 2021-10-25) (only part of the range) (US), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

Not in ARIN-Issued Removed (return, revocation or reclamation not publicly distinguishable)

Reported
2011-12-28 (ARIN)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2011-12-28 (ARIN)
Estimated hold end
2012-02-26 (from ARIN's published rule)
Now
Possible reissue candidate; not confirmed available.

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.

2011-12-28 ARIN Not in ARIN-Issued Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2012-02-26. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. ARIN-Issued didn't list this; the tracker found it by comparing ARIN's daily statistics. ARIN's statistics show it allocated (dated 1999-11-03) on 2011-12-27 and not issued on 2011-12-29. (Until 2013-03-05, ARIN's statistics list only what's issued.) Public sources do not distinguish a voluntary return, revocation, or reclamation. ARIN holds returned, revoked and reclaimed IPv4 space for 60 days before reissuing it, so the estimated hold end is 2012-02-26. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Not listed in ARIN-Issued; found by comparing ARIN's daily statistics: 216.250.96.0/20 allocated on 2011-12-28, not listed on 2011-12-29 source · retrieved
  2. Before ARIN delegated statistics 2011-12-27, before the report: allocated (dated 1999-11-03) source · retrieved
  3. After ARIN delegated statistics 2011-12-29, after the report: not issued source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-06-26ARIN216.250.99.0/24Transfer logMerger/acquisition
2025-10-17APNIC216.250.100.0/22Transfer logIntra-APNIC transfer
2021-10-26APNIC216.250.99.0/24Transfer logTransfer out of APNIC
2021-10-25ARIN216.250.99.0/24+ AddTransfer into ARIN
2019-03-25APNIC216.250.108.0/22Transfer logIntra-APNIC transfer
2018-07-06APNIC216.250.98.0/24Transfer logIntra-APNIC transfer
2016-09-05APNIC216.250.96.0/22+ RegisteredApparent new issuance
2016-09-05APNIC216.250.100.0/22+ RegisteredApparent new issuance
2016-09-05APNIC216.250.104.0/22+ RegisteredApparent new issuance
2016-09-05APNIC216.250.108.0/22+ RegisteredApparent new issuance

Transfer records (6)

Date (UTC)LogTypeRange movedFromTo
ARINMerger acquisition216.250.99.0/24 Disaster Networks, LLC ARINNetwork Advisors, LLC ARIN
APNICResource transfer216.250.100.0/22 WifiCity, Inc APNICIgnite Telecommunications Inc APNIC
APNICResource transfer216.250.99.0/24 HostHatch LLC APNICDNL-53 ARIN
ARINResource transfer216.250.99.0/24 HostHatch, Inc APNICDisaster Networks, LLC ARIN
APNICResource transfer216.250.108.0/22 Ningpu Pure Day Network Co., Ltd. APNICDingFeng XinHui (HongKong) Technology Limited APNIC
APNICResource transfer216.250.98.0/24 HostHatch LLC APNICEvolution Wireless Ltd APNIC

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/216.250.96.0-216.250.111.255.json