rirtracker

IPv6 range · 79,228,162,514,264,337,593,543,950,336 addresses

2a01:4cc0::/32

Now

RIPE NCC statistics
Available, in the latest file
Registry
RIPE NCC
Holder
None: it's in the registry's own pool
From
The RIPE NCC's latest statistics

Latest change

− Deregistered Removed (return, revocation or reclamation not publicly distinguishable)

Reported
2025-07-21 (RIPE NCC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2025-07-21 (RIPE NCC)
Estimated hold end
2026-01-17 (from the RIPE NCC's published rule; or later while it's still routed)
Now
Possible reissue candidate; not confirmed available.

Timeline (3)

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-07-21 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a01:4cc0::/32 allocated on 2025-07-20, reserved on 2025-07-21
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2026-01-17. 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 2012-05-29) on 2025-07-20 and reserved on 2025-07-21. 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-01-17. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a01:4cc0::/32 allocated on 2025-07-20, reserved on 2025-07-21 source · retrieved
  2. Before RIPE NCC delegated statistics 2025-07-20 (produced 2025-07-20T21:59:59+00:00), before the change: allocated (dated 2012-05-29) source · retrieved
  3. After RIPE NCC delegated statistics 2025-07-21 (produced 2025-07-21T21:59:59+00:00), after the change: reserved 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
2017-10-20 RIPE NCC Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: Outsourcery Hosting LTD (RIPE NCC) to GCI Network Solutions Limited (RIPE NCC)
From
Outsourcery Hosting LTD RIPE NCC
To
GCI Network Solutions Limited RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a merger, acquisition or reorganization from Outsourcery Hosting LTD (RIPE NCC) to GCI Network Solutions Limited (RIPE NCC) on 2017-10-20 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: MERGER_ACQUISITION on 2017-10-20 19:00 UTC, Outsourcery Hosting LTD (RIPE NCC) to GCI Network Solutions Limited (RIPE NCC); resources moved: 2a01:4cc0::/32 source · retrieved
  2. Before RIPE NCC delegated statistics 2017-10-19 (produced 2017-10-19T21:59:59+00:00), before the change: allocated (dated 2012-05-29) source · retrieved
  3. After RIPE NCC delegated statistics 2017-10-20 (produced 2017-10-20T21:59:59+00:00), after the change: allocated (dated 2012-05-29) source · retrieved
Classification history for this change (4 versions)
  1. : Merger/acquisition or reorganization, confirmed (classifier 1.3.0)
  2. : Merger/acquisition or reorganization, confirmed (classifier 1.3.1)
  3. : Merger/acquisition or reorganization, confirmed (classifier 1.3.2)
  4. : Merger/acquisition or reorganization, confirmed (classifier 1.4.0) current
2012-05-29 RIPE NCC + Registered Apparent new issuance Strong inference
Statistics
2a01:4cc0::/32 available on 2012-05-28, allocated on 2012-05-29
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2012-05-28 and allocated (dated 2012-05-29) on 2012-05-29. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a01:4cc0::/32 available on 2012-05-28, allocated on 2012-05-29 source · retrieved
  2. Before RIPE NCC delegated statistics 2012-05-28 (produced 2012-05-28T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2012-05-29 (produced 2012-05-29T21:59:59+00:00), after the change: allocated (dated 2012-05-29) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent new issuance, strong inference (classifier 1.3.0)
  2. : Apparent new issuance, strong inference (classifier 1.3.1)
  3. : Apparent new issuance, strong inference (classifier 1.3.2)
  4. : Apparent new issuance, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-01-17RIPE NCC2a01:4cc0::/27ReleasedHold released

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCMerger acquisition2a01:4cc0::/32 Outsourcery Hosting LTD RIPE NCCGCI Network Solutions Limited RIPE NCC

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.

This page as data: ip/2a01.4cc0..-2a01.4cc0.ffff.ffff.ffff.ffff.ffff.ffff.json