rirtracker

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

2001:5::/32

Now

RIPE NCC statistics
Not listed, in the latest file
Registry
Not known
Holder
Not looked up

Latest change

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

Reported
2019-09-11 (RIPE NCC)
Confidence
Observed only
Inventory
Possible future reissue candidate after hold

Hold

Removed
2019-09-11 (RIPE NCC)
Estimated hold end
2020-03-09 (from the RIPE NCC's published rule; or later while it's still routed)
Now
Possible reissue candidate; not confirmed available.

Timeline (2)

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.

2019-09-11 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Observed only
Statistics
2001:5::/32 allocated on 2019-09-10, not listed on 2019-09-11
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2020-03-09. 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 2016-11-15) on 2019-09-10 and not listed on 2019-09-11. Being gone from the RIPE NCC's statistics entirely can also mean it moved to another registry. 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 2020-03-09. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2001:5::/32 allocated on 2019-09-10, not listed on 2019-09-11 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-09-10 (produced 2019-09-10T21:59:59+00:00), before the change: allocated (dated 2016-11-15) source · retrieved
  3. After RIPE NCC delegated statistics 2019-09-11 (produced 2019-09-11T21:59:59+00:00), after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.4.0) current
2016-11-15 RIPE NCC + Registered Unresolved change Observed only
Statistics
2001:5::/32 not listed on 2016-11-14, allocated on 2016-11-15
Inventory
Inventory effect unknown

No transfer record matches. The RIPE NCC's statistics show it not listed on 2016-11-14 and allocated (dated 2016-11-15) on 2016-11-15. It wasn't in the RIPE NCC's statistics before, so it wasn't the RIPE NCC's unissued inventory; it may have come from another registry in a transfer not yet in the log.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2001:5::/32 not listed on 2016-11-14, allocated on 2016-11-15 source · retrieved
  2. Before RIPE NCC delegated statistics 2016-11-14 (produced 2016-11-14T22:59:59+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2016-11-15 (produced 2016-11-15T22:59:59+00:00), after the change: allocated (dated 2016-11-15) source · retrieved
Classification history for this change (4 versions)
  1. : Unresolved change, observed only (classifier 1.3.0)
  2. : Unresolved change, observed only (classifier 1.3.1)
  3. : Unresolved change, observed only (classifier 1.3.2)
  4. : Unresolved change, observed only (classifier 1.4.0) current

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/2001.5..-2001.5.ffff.ffff.ffff.ffff.ffff.ffff.json