This data was last updated ago, at . The site normally updates once a day, so the latest update didn't finish; recent changes may be missing.
Source delay.
Conclusions that depend on it may be incomplete; see Sources.
IPv4 range · 4,194,304 addresses
176.0.0.0/10
Now
RIPE NCC statistics
Allocated (234 records, dated 2011-05-13 to 2025-01-29), reserved (1 record) (AE, AM, AT, AZ, BE, BG, BY, CA, CH, CZ, DE, DK, EE, ES, FR, GB, GR, HK, HR, HU, IE, IL, IQ, IR, IS, IT, JO, LV, NL, NO, PL, PS, PT, RO, RU, SA, SC, SE, SI, SK, TR, UA, US), in the latest file
Registry
Not known
Holder
Not looked up
Latest change
− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)
Not estimated: the RIPE NCC's current hold applies to removals from 2014-03-26 on, and this one came earlier
Now
Possible reissue candidate; not confirmed available.
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.
2011-03-08RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
176.0.0.0/10 allocated on 2011-03-07, available on 2011-03-08
Inventory
Possible future reissue candidate after hold
Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2009-09-18) on 2011-03-07 and available on 2011-03-08. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC's current hold for IPv4 space applies to removals from 2014-03-26 on, and this one came earlier, so the tracker gives no estimate. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 176.0.0.0/10 allocated on 2011-03-07, available on 2011-03-08source · retrieved
BeforeRIPE NCC delegated statistics 2011-03-07, before the change: allocated (dated 2009-09-18)source · retrieved
AfterRIPE NCC delegated statistics 2011-03-08, after the change: availablesource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2011-03-01RIPE NCC+ RegisteredUnresolved changeObserved only
Statistics
176.0.0.0/10 available on 2011-02-28, allocated on 2011-03-01
Inventory
Inventory effect unknown
No transfer record matches. The RIPE NCC's statistics show it available on 2011-02-28 and allocated (dated 2009-09-18) on 2011-03-01. The new registration isn't dated near that day, so the tracker can't tell whether this is a new issuance.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 176.0.0.0/10 available on 2011-02-28, allocated on 2011-03-01source · retrieved
BeforeRIPE NCC delegated statistics 2011-02-28, before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2011-03-01, after the change: allocated (dated 2009-09-18)source · retrieved
Classification history for this change (4 versions)
: Unresolved change, observed only (classifier 1.3.0)
: Unresolved change, observed only (classifier 1.3.1)
: Unresolved change, observed only (classifier 1.3.2)
: Unresolved change, observed only (classifier 1.4.0) current
Ruzgar Teknik Yazilim Bilisim Limited Sirketi RIPE NCC
Hop Bilisim Teknolojileri Anonim Sirketi 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.