rirtracker

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

2a00:e3a0::/32

Now

RIPE NCC statistics
Reserved on 2026-10-09
Registry
Not known
Holder
Not looked up

Latest change

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

Reported
2026-05-04 (RIPE NCC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2026-05-04 (RIPE NCC)
Estimated hold end
Not estimated: RIPE NCC publishes no fixed hold period
Now
Possible reissue candidate; not confirmed available.

Timeline since 2026-01-01 (1)

2026-05-04 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a00:e3a0::/32 allocated on 2026-05-03, reserved on 2026-05-04
Inventory
Possible future reissue candidate after hold

Removed from active registration. The tracker found it by comparing RIPE NCC's daily statistics. RIPE NCC's statistics show it allocated (dated 2013-09-18) on 2026-05-03 and reserved on 2026-05-04. Public sources do not distinguish a voluntary return, revocation, or reclamation. RIPE NCC publishes no fixed period for which it holds returned IPv6 before reissuing them, so the tracker gives no estimate. This does not confirm availability.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 2a00:e3a0::/32 allocated on 2026-05-03, reserved on 2026-05-04 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-05-03 (produced 2026-05-03T21:59:59+00:00), before the change: allocated (dated 2013-09-18) source · retrieved
  3. After RIPE NCC delegated statistics 2026-05-04 (produced 2026-05-04T21:59:59+00:00), after the change: reserved source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a00:e3a0::/32 Tribe Technology Aps RIPE NCCNetexpon ApS RIPE NCC

Every record in the ARIN and RIPE NCC transfer logs that moved any part of this IPv6 range (ARIN's go back to 2009, the RIPE NCC's to 2012). 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.e3a0..-2a00.e3a0.ffff.ffff.ffff.ffff.ffff.ffff.json