rirtracker

IPv6 range · 79,228,162,514,264,337,593,543,950,336 addresses

2a00:5440::/32

Now

RIPE NCC statistics
Allocated (dated 2011-12-07) on 2026-10-09 (GB)
Registry
RIPE NCC
Holder
Rackspace Ltd.
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-03-12 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-03-12 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Datapipe Europe Ltd (RIPE NCC) to Rackspace Ltd. (RIPE NCC)
From
Datapipe Europe Ltd RIPE NCC
To
Rackspace Ltd. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Datapipe Europe Ltd (RIPE NCC) to Rackspace Ltd. (RIPE NCC) on 2026-03-12 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-03-12 19:00 UTC, Datapipe Europe Ltd (RIPE NCC) to Rackspace Ltd. (RIPE NCC); resources moved: 2a00:5440::/32 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-03-11 (produced 2026-03-11T22:59:59+00:00), before the change: allocated (dated 2011-12-07) source · retrieved
  3. After RIPE NCC delegated statistics 2026-03-12 (produced 2026-03-12T22:59:59+00:00), after the change: allocated (dated 2011-12-07) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a00:5440::/32 Datapipe Europe Ltd RIPE NCCRackspace Ltd. 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/2a00.5440..-2a00.5440.ffff.ffff.ffff.ffff.ffff.ffff.json