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.
Transfer: FS LLC (RIPE NCC) to MB Manding Data Venture (RIPE NCC)
From
FS LLC RIPE NCC
To
MB Manding Data Venture RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from FS LLC (RIPE NCC) to MB Manding Data Venture (RIPE NCC) on 2025-06-24 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2025-06-24 19:00 UTC, FS LLC (RIPE NCC) to MB Manding Data Venture (RIPE NCC); resources moved: 2a02:e9c0::/29source · retrieved
BeforeRIPE NCC delegated statistics 2025-06-23 (produced 2025-06-23T21:59:59+00:00), before the change: allocated (dated 2024-05-29)source · retrieved
AfterRIPE NCC delegated statistics 2025-06-24 (produced 2025-06-24T21:59:59+00:00), after the change: allocated (dated 2024-05-29)source · retrieved
Classification history for this change (4 versions)
: Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
2024-05-29RIPE NCC+ RegisteredApparent reissuance of previously removed resourceObserved only
Statistics
2a02:e9c0::/29 available on 2024-05-28, allocated on 2024-05-29
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2024-05-28 and allocated (dated 2024-05-29) on 2024-05-29. The tracker saw this range removed from registration on 2023-11-30 (2a02:e9c0::/29), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2024-05-28: Released 2a02:e9c0::/26), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a02:e9c0::/29 available on 2024-05-28, allocated on 2024-05-29source · retrieved
BeforeRIPE NCC delegated statistics 2024-05-28 (produced 2024-05-28T21:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2024-05-29 (produced 2024-05-29T21:59:59+00:00), after the change: allocated (dated 2024-05-29)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
: Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current
2023-11-30RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
2a02:e9c0::/29 allocated on 2023-11-29, reserved on 2023-11-30
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2024-05-28. 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 2012-11-26) on 2023-11-29 and reserved on 2023-11-30. 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 2024-05-28. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a02:e9c0::/29 allocated on 2023-11-29, reserved on 2023-11-30source · retrieved
BeforeRIPE NCC delegated statistics 2023-11-29 (produced 2023-11-29T22:59:59+00:00), before the change: allocated (dated 2012-11-26)source · retrieved
AfterRIPE NCC delegated statistics 2023-11-30 (produced 2023-11-30T22:59:59+00:00), after the change: reservedsource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2012-11-26RIPE NCC+ RegisteredApparent new issuanceStrong inference
Statistics
2a02:e9c0::/29 available on 2012-11-25, allocated on 2012-11-26
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2012-11-25 and allocated (dated 2012-11-26) on 2012-11-26. 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,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2a02:e9c0::/29 available on 2012-11-25, allocated on 2012-11-26source · retrieved
BeforeRIPE NCC delegated statistics 2012-11-25 (produced 2012-11-25T22:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2012-11-26 (produced 2012-11-26T22:59:59+00:00), after the change: allocated (dated 2012-11-26)source · retrieved
Classification history for this change (4 versions)
: Apparent new issuance, strong inference (classifier 1.3.0)
: Apparent new issuance, strong inference (classifier 1.3.1)
: Apparent new issuance, strong inference (classifier 1.3.2)
: Apparent new issuance, strong inference (classifier 1.4.0) current
Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv6 range (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). 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.