rirtracker

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

2a0d::/29

Now

RIPE NCC statistics
Allocated (dated 2026-08-19), reserved on 2026-10-09 (RU)
Registry
Not known
Holder
Not looked up

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-02-19 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-02-19 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: WIRELESS COMMUNICATION, S.L. (RIPE NCC) to Free Technologies Excom S.L. (RIPE NCC)
From
WIRELESS COMMUNICATION, S.L. RIPE NCC
To
Free Technologies Excom S.L. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from WIRELESS COMMUNICATION, S.L. (RIPE NCC) to Free Technologies Excom S.L. (RIPE NCC) on 2026-02-19 19:00 UTC. The registration changed hands; it is not a new allocation from RIPE NCC.

Evidence (3) · classifier 1.1.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-02-19 19:00 UTC, WIRELESS COMMUNICATION, S.L. (RIPE NCC) to Free Technologies Excom S.L. (RIPE NCC); resources moved: 2a0d::/29 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-02-18 (produced 2026-02-18T22:59:59+00:00), before the change: allocated (dated 2017-09-15) source · retrieved
  3. After RIPE NCC delegated statistics 2026-02-19 (produced 2026-02-19T22:59:59+00:00), after the change: reserved source · retrieved

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-08-19RIPE NCC2a0d::/32+ RegisteredApparent new issuance
2026-08-18RIPE NCC2a0d::/26ReleasedRIPE NCC pool record

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a0d::/29 WIRELESS COMMUNICATION, S.L. RIPE NCCFree Technologies Excom S.L. 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.

This page as data: ip/2a0d..-2a0d.7.ffff.ffff.ffff.ffff.ffff.ffff.json