rirtracker

IPv6 range · 633,825,300,114,114,700,748,351,602,688 addresses

2a13:a980::/29

Now

RIPE NCC statistics
Reserved, in the latest file
Registry
RIPE NCC
Holder
RIPE Network Coordination Center ORG-NCC1-RIPE
From
RDAP, looked up 2026-11-05 18:24 UTC

Latest change

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

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

Hold

Removed
2026-10-28 (RIPE NCC)
Estimated hold end
2027-04-26 (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.

2026-10-28 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a13:a980::/29 allocated on 2026-10-27, reserved on 2026-10-28
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2027-04-26. 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 2023-03-02) on 2026-10-27 and reserved on 2026-10-28. 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 2027-04-26. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a13:a980::/29 allocated on 2026-10-27, reserved on 2026-10-28 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-10-27 (produced 2026-10-27T22:59:59+00:00), before the change: allocated (dated 2023-03-02) source · retrieved
  3. After RIPE NCC delegated statistics 2026-10-28 (produced 2026-10-28T22:59:59+00:00), after the change: reserved source · retrieved
2023-03-02 RIPE NCC + Registered Apparent new issuance Strong inference
Statistics
2a13:a980::/29 available on 2023-03-01, allocated on 2023-03-02
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2023-03-01 and allocated (dated 2023-03-02) on 2023-03-02. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a13:a980::/29 available on 2023-03-01, allocated on 2023-03-02 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-03-01 (produced 2023-03-01T22:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2023-03-02 (produced 2023-03-02T22:59:59+00:00), after the change: allocated (dated 2023-03-02) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent new issuance, strong inference (classifier 1.3.0)
  2. : Apparent new issuance, strong inference (classifier 1.3.1)
  3. : Apparent new issuance, strong inference (classifier 1.3.2)
  4. : Apparent new issuance, strong inference (classifier 1.4.0) current

Transfer records

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

RDAP lookups

Looked upWhyRegistryHandleOrganizationStatusLast changed
After 7 days RIPE NCC2a00::/11RIPE Network Coordination Center ORG-NCC1-RIPEactive2019-06-06
After 24 hours RIPE NCC2a00::/11RIPE Network Coordination Center ORG-NCC1-RIPEactive2019-06-06
First seen RIPE NCC2a00::/11RIPE Network Coordination Center ORG-NCC1-RIPEactive2019-06-06

Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.

This page as data: ip/2a13.a980..-2a13.a987.ffff.ffff.ffff.ffff.ffff.ffff.json