rirtracker

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

2a00:1e60::/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-15 (RIPE NCC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2025-07-15 (RIPE NCC)
Estimated hold end
2026-01-11 (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-15 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a00:1e60::/32 allocated on 2025-07-14, reserved on 2025-07-15
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2026-01-11. 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 2010-04-07) on 2025-07-14 and reserved on 2025-07-15. 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-11. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a00:1e60::/32 allocated on 2025-07-14, reserved on 2025-07-15 source · retrieved
  2. Before RIPE NCC delegated statistics 2025-07-14 (produced 2025-07-14T21:59:59+00:00), before the change: allocated (dated 2010-04-07) source · retrieved
  3. After RIPE NCC delegated statistics 2025-07-15 (produced 2025-07-15T21: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
2024-06-20 RIPE NCC Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: Nej.cz s.r.o. (RIPE NCC) to O2 Czech Republic, a.s. (RIPE NCC)
From
Nej.cz s.r.o. RIPE NCC
To
O2 Czech Republic, a.s. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a merger, acquisition or reorganization from Nej.cz s.r.o. (RIPE NCC) to O2 Czech Republic, a.s. (RIPE NCC) on 2024-06-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 2024-06-20 19:00 UTC, Nej.cz s.r.o. (RIPE NCC) to O2 Czech Republic, a.s. (RIPE NCC); resources moved: 2a00:1e60::/32 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-06-19 (produced 2024-06-19T21:59:59+00:00), before the change: allocated (dated 2010-04-07) source · retrieved
  3. After RIPE NCC delegated statistics 2024-06-20 (produced 2024-06-20T21:59:59+00:00), after the change: allocated (dated 2010-04-07) 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
2020-08-19 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: CATR spol. s r.o. (RIPE NCC) to Nej.cz s.r.o. (RIPE NCC)
From
CATR spol. s r.o. RIPE NCC
To
Nej.cz s.r.o. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from CATR spol. s r.o. (RIPE NCC) to Nej.cz s.r.o. (RIPE NCC) on 2020-08-19 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: RESOURCE_TRANSFER on 2020-08-19 19:00 UTC, CATR spol. s r.o. (RIPE NCC) to Nej.cz s.r.o. (RIPE NCC); resources moved: 2a00:1e60::/32 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-08-18 (produced 2020-08-18T21:59:59+00:00), before the change: allocated (dated 2010-04-07) source · retrieved
  3. After RIPE NCC delegated statistics 2020-08-19 (produced 2020-08-19T21:59:59+00:00), after the change: allocated (dated 2010-04-07) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-01-11RIPE NCC2a00:1e60::/29ReleasedHold released

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCMerger acquisition2a00:1e60::/32 Nej.cz s.r.o. RIPE NCCO2 Czech Republic, a.s. RIPE NCC
RIPE NCCResource transfer2a00:1e60::/32 CATR spol. s r.o. RIPE NCCNej.cz s.r.o. 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/2a00.1e60..-2a00.1e60.ffff.ffff.ffff.ffff.ffff.ffff.json