rirtracker

IPv6 range · 1,208,925,819,614,629,174,706,176 addresses

2001:7f8:aa::/48

Now

RIPE NCC statistics
Assigned (dated 2026-08-31) on 2026-10-09 (GB)
Registry
RIPE NCC
Holder
Not looked up
From
RIPE NCC's statistics for 2026-10-09

Latest change

+ Registered Apparent reissuance of previously removed resource

Reported
2026-08-31 (RIPE NCC)
Confidence
Strong inference
Inventory
Likely issued from RIPE NCC-controlled inventory

Hold

Removed
2026-01-15 (RIPE NCC)
Estimated hold end
Not estimated: RIPE NCC publishes no fixed hold period

Timeline since 2026-01-01 (3)

2026-08-31 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
2001:7f8:aa::/48 available on 2026-08-30, assigned on 2026-08-31
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. RIPE NCC's statistics show it available on 2026-08-30 and assigned (dated 2026-08-31) on 2026-08-31. The tracker saw this range removed from registration on 2026-01-15 (2001:7f8:aa::/48), so it appears to have been issued again from RIPE NCC's pool.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 2001:7f8:aa::/48 available on 2026-08-30, assigned on 2026-08-31 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-08-30 (produced 2026-08-30T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2026-08-31 (produced 2026-08-31T21:59:59+00:00), after the change: assigned (dated 2026-08-31) source · retrieved
2026-07-14 RIPE NCC Released Released from hold (RIPE NCC lists it as 'available') Strong inference
Statistics
2001:7f8:aa::/48 reserved on 2026-07-13, available on 2026-07-14
Inventory
RIPE NCC's statistics now list it as 'available'; reissue not confirmed

RIPE NCC's statistics show it reserved on 2026-07-13 and available on 2026-07-14. RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2026-01-15, 180 days earlier. That is RIPE NCC's own label: whether and when it is reissued is not confirmed.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 2001:7f8:aa::/48 reserved on 2026-07-13, available on 2026-07-14 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-07-13 (produced 2026-07-13T21:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2026-07-14 (produced 2026-07-14T21:59:59+00:00), after the change: available source · retrieved
2026-01-15 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2001:7f8:aa::/48 assigned on 2026-01-14, reserved on 2026-01-15
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 assigned (dated 2017-02-20) on 2026-01-14 and reserved on 2026-01-15. 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: 2001:7f8:aa::/48 assigned on 2026-01-14, reserved on 2026-01-15 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-01-14 (produced 2026-01-14T22:59:59+00:00), before the change: assigned (dated 2017-02-20) source · retrieved
  3. After RIPE NCC delegated statistics 2026-01-15 (produced 2026-01-15T22:59:59+00:00), after the change: reserved source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2001:7f8:aa::/48 Interlan Networks AB RIPE NCCInterlan Gefle AB 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/2001.7f8.aa..-2001.7f8.aa.ffff.ffff.ffff.ffff.ffff.json