This data was last updated ago, at 2026-10-10 17:51 UTC. The site normally updates once a day, so the latest update didn't finish; recent changes may be missing.
IPv6 range · 633,825,300,114,114,700,748,351,602,688 addresses
2a0b:9340::/29
Now
RIPE NCC statistics
Reserved on 2026-10-09
Registry
Not known
Holder
Not looked up
Latest change
− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)
Not estimated: RIPE NCC publishes no fixed hold period
Now
Possible reissue candidate; not confirmed available.
Timeline since 2026-01-01 (2)
2026-10-01RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
2a0b:9340::/29 allocated on 2026-09-30, reserved on 2026-10-01
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 allocated (dated 2026-04-20) on 2026-09-30 and reserved on 2026-10-01. 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,
StatisticsFound by comparing RIPE NCC's daily statistics: 2a0b:9340::/29 allocated on 2026-09-30, reserved on 2026-10-01source · retrieved
BeforeRIPE NCC delegated statistics 2026-09-30 (produced 2026-09-30T21:59:59+00:00), before the change: allocated (dated 2026-04-20)source · retrieved
AfterRIPE NCC delegated statistics 2026-10-01 (produced 2026-10-01T21:59:59+00:00), after the change: reservedsource · retrieved
2026-04-20RIPE NCC+ RegisteredApparent new issuanceObserved only
Statistics
2a0b:9340::/29 available on 2026-04-19, allocated on 2026-04-20
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. RIPE NCC's statistics show it available on 2026-04-19 and allocated (dated 2026-04-20) on 2026-04-20. It moved from RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by RIPE NCC. Another change to this range was reported the day before or after (2026-04-19: Released 2a0b:9340::/26), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.1.0,
StatisticsFound by comparing RIPE NCC's daily statistics: 2a0b:9340::/29 available on 2026-04-19, allocated on 2026-04-20source · retrieved
BeforeRIPE NCC delegated statistics 2026-04-19 (produced 2026-04-19T21:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2026-04-20 (produced 2026-04-20T21:59:59+00:00), after the change: allocated (dated 2026-04-20)source · retrieved
COMUNICACIONES E INFRAESTRUCTURAS DEL SUR SL 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.