rirtracker

IPv6 range · 5,070,602,400,912,917,605,986,812,821,504 addresses

2a04:e1c0::/26

Now

RIPE NCC statistics
Allocated (dated 2025-12-02), reserved (CZ), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

Released Released from hold (the RIPE NCC lists it as 'available')

Reported
2025-12-01 (RIPE NCC)
Confidence
Observed only
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

Hold

Released from hold
2025-12-01
Now
Possible reissue candidate; not confirmed available.

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.

2025-12-01 RIPE NCC Released Released from hold (the RIPE NCC lists it as 'available') Observed only
Statistics
2a04:e1c0::/26 reserved on 2025-11-30, available on 2025-12-01
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

The RIPE NCC's statistics show it reserved on 2025-11-30 and available on 2025-12-01. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2025-06-04, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed. Another change to this range was reported the day before or after (2025-12-02: Added 2a04:e1c0::/31), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a04:e1c0::/26 reserved on 2025-11-30, available on 2025-12-01 source · retrieved
  2. Before RIPE NCC delegated statistics 2025-11-30 (produced 2025-11-30T22:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2025-12-01 (produced 2025-12-01T22:59:59+00:00), after the change: available source · retrieved
Classification history for this change (4 versions)
  1. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.0)
  2. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.1)
  3. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.2)
  4. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2025-12-02RIPE NCC2a04:e1c0::/31+ RegisteredApparent reissuance
2025-06-04RIPE NCC2a04:e1c0::/29− DeregisteredRemoved
2024-12-20RIPE NCC2a04:e1c0::/29Transfer logIntra-RIPE NCC transfer
2022-09-22RIPE NCC2a04:e1c0::/29Transfer logMerger/acquisition
2014-05-23RIPE NCC2a04:e1c0::/29+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a04:e1c0::/29 Protagonist B.V. RIPE NCCQweb Internet Services B.V. RIPE NCC
RIPE NCCMerger acquisition2a04:e1c0::/29 Mijnserver BV RIPE NCCProtagonist B.V. 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/2a04.e1c0..-2a04.e1ff.ffff.ffff.ffff.ffff.ffff.ffff.json