The RIPE NCC's statistics now list it as 'available'; reissue not confirmed
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.
2023-09-25RIPE NCCReleasedChange to the RIPE NCC's own pool recordObserved only
Statistics
2a0c:db40::/26 reserved on 2023-09-24, available on 2023-09-25
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed
The RIPE NCC's statistics show it reserved on 2023-09-24 and available on 2023-09-25. The RIPE NCC keeps reserved IPv6 space next to its allocations for their growth, and the tracker didn't see this range removed from registration, so this is most likely the RIPE NCC returning such space to its pool, not a hold ending. Another change to this range was reported the day before or after (2023-09-26: Added 2a0c:db40::/29), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a0c:db40::/26 reserved on 2023-09-24, available on 2023-09-25source · retrieved
BeforeRIPE NCC delegated statistics 2023-09-24 (produced 2023-09-24T21:59:59+00:00), before the change: reservedsource · retrieved
AfterRIPE NCC delegated statistics 2023-09-25 (produced 2023-09-25T21:59:59+00:00), after the change: availablesource · retrieved
Classification history for this change (4 versions)
: Change to the RIPE NCC's own pool record, observed only (classifier 1.3.0)
: Change to the RIPE NCC's own pool record, observed only (classifier 1.3.1)
: Change to the RIPE NCC's own pool record, observed only (classifier 1.3.2)
: Change to the RIPE NCC's own pool record, observed only (classifier 1.4.0) current
Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv6 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.