rirtracker

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

2a05:cb80::/26

Now

RIPE NCC statistics
Allocated (dated 2026-07-21), reserved on 2026-10-09 (TR)
Registry
Not known
Holder
Not looked up

Latest change

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

Reported
2026-07-20 (RIPE NCC)
Confidence
Observed only
Inventory
RIPE NCC's statistics now list it as 'available'; reissue not confirmed

Hold

Released from hold
2026-07-20
Now
Possible reissue candidate; not confirmed available.

Timeline since 2026-01-01 (1)

2026-07-20 RIPE NCC Released Released from hold (RIPE NCC lists it as 'available') Observed only
Statistics
2a05:cb80::/26 reserved on 2026-07-19, available on 2026-07-20
Inventory
RIPE NCC's statistics now list it as 'available'; reissue not confirmed

RIPE NCC's statistics show it reserved on 2026-07-19 and available on 2026-07-20. 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-21, 180 days earlier. That is 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 (2026-07-21: Added 2a05:cb80::/29), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 2a05:cb80::/26 reserved on 2026-07-19, available on 2026-07-20 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-07-19 (produced 2026-07-19T21:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2026-07-20 (produced 2026-07-20T21:59:59+00:00), after the change: available source · retrieved

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-07-21RIPE NCC2a05:cb80::/29+ RegisteredApparent reissuance
2026-01-21RIPE NCC2a05:cb80::/29− DeregisteredRemoved

Transfer records

No transfer log has a transfer of any part of this IPv6 range.

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/2a05.cb80..-2a05.cbbf.ffff.ffff.ffff.ffff.ffff.ffff.json