rirtracker

IPv6 range · 5,070,602,400,912,917,605,986,812,821,504 addresses

2a06:5200::/26

Now

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

Latest change

Released Change to RIPE NCC's own pool record

Reported
2026-01-06 (RIPE NCC)
Confidence
Strong inference
Inventory
RIPE NCC's statistics now list it as 'available'; reissue not confirmed

Timeline since 2026-01-01 (1)

2026-01-06 RIPE NCC Released Change to RIPE NCC's own pool record Strong inference
Statistics
2a06:5200::/26 reserved on 2026-01-05, available on 2026-01-06
Inventory
RIPE NCC's statistics now list it as 'available'; reissue not confirmed

RIPE NCC's statistics show it reserved on 2026-01-05 and available on 2026-01-06. RIPE NCC keeps reserved IPv6 space next to its allocations for their growth, and the tracker didn't see this range removed from registration, so this is most likely RIPE NCC returning such space to its pool, not a hold ending.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 2a06:5200::/26 reserved on 2026-01-05, available on 2026-01-06 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-01-05 (produced 2026-01-05T22:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2026-01-06 (produced 2026-01-06T22:59:59+00:00), after the change: available source · retrieved

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-01-08RIPE NCC2a06:5200::/29+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCMerger acquisition2a06:5200::/29 CLDIN B.V. RIPE NCCYour hosting B.V. RIPE NCC
RIPE NCCMerger acquisition2a06:5200::/29 PCextreme B.V. RIPE NCCCLDIN B.V. 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/2a06.5200..-2a06.523f.ffff.ffff.ffff.ffff.ffff.ffff.json