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-10-23RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
2a06:8200::/32 allocated on 2025-10-22, reserved on 2025-10-23
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2026-04-21. Possible reissue candidate after this date; not confirmed available.
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 2019-02-04) on 2025-10-22 and reserved on 2025-10-23. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv6 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2026-04-21. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a06:8200::/32 allocated on 2025-10-22, reserved on 2025-10-23source · retrieved
BeforeRIPE NCC delegated statistics 2025-10-22 (produced 2025-10-22T21:59:59+00:00), before the change: allocated (dated 2019-02-04)source · retrieved
AfterRIPE NCC delegated statistics 2025-10-23 (produced 2025-10-23T21:59:59+00:00), after the change: reservedsource · 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
2019-02-04RIPE NCC+ RegisteredApparent reissuance of previously removed resourceObserved only
Statistics
2a06:8200::/32 available on 2019-02-03, allocated on 2019-02-04
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2019-02-03 and allocated (dated 2019-02-04) on 2019-02-04. The tracker saw this range removed from registration on 2018-08-07 (2a06:8200::/29), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2019-02-03: Released 2a06:8200::/26), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a06:8200::/32 available on 2019-02-03, allocated on 2019-02-04source · retrieved
BeforeRIPE NCC delegated statistics 2019-02-03 (produced 2019-02-03T22:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2019-02-04 (produced 2019-02-04T22:59:59+00:00), after the change: allocated (dated 2019-02-04)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
: Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current
No transfer log has a transfer of any part of this IPv6 range.
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.