rirtracker

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

2a0b:cd40::/32

Now

RIPE NCC statistics
Reserved, in the latest file
Registry
RIPE NCC
Holder
None: it's in the registry's own pool
From
The RIPE NCC's latest statistics

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2020-05-08 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline (2)

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.

2020-05-08 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: CIS Operations AG (RIPE NCC) to Beelastic AG (RIPE NCC)
From
CIS Operations AG RIPE NCC
To
Beelastic AG RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from CIS Operations AG (RIPE NCC) to Beelastic AG (RIPE NCC) on 2020-05-08 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2020-05-08 19:00 UTC, CIS Operations AG (RIPE NCC) to Beelastic AG (RIPE NCC); resources moved: 2a0b:cd40::/32 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-05-07 (produced 2020-05-07T21:59:59+00:00), before the change: allocated (dated 2017-08-17) source · retrieved
  3. After RIPE NCC delegated statistics 2020-05-08 (produced 2020-05-08T21:59:59+00:00), after the change: allocated (dated 2017-08-17) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
2017-08-17 RIPE NCC + Registered Apparent new issuance Strong inference
Statistics
2a0b:cd40::/32 available on 2017-08-16, allocated on 2017-08-17
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2017-08-16 and allocated (dated 2017-08-17) on 2017-08-17. 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,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a0b:cd40::/32 available on 2017-08-16, allocated on 2017-08-17 source · retrieved
  2. Before RIPE NCC delegated statistics 2017-08-16 (produced 2017-08-16T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2017-08-17 (produced 2017-08-17T21:59:59+00:00), after the change: allocated (dated 2017-08-17) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent new issuance, strong inference (classifier 1.3.0)
  2. : Apparent new issuance, strong inference (classifier 1.3.1)
  3. : Apparent new issuance, strong inference (classifier 1.3.2)
  4. : Apparent new issuance, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-06-18RIPE NCC2a0b:cd40::/29− DeregisteredRemoved
2024-03-05RIPE NCC2a0b:cd40::/29+ RegisteredApparent reissuance
2024-03-04RIPE NCC2a0b:cd40::/26ReleasedHold released
2023-09-06RIPE NCC2a0b:cd40::/29− DeregisteredRemoved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a0b:cd40::/32 CIS Operations AG RIPE NCCBeelastic AG RIPE NCC

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.

This page as data: ip/2a0b.cd40..-2a0b.cd40.ffff.ffff.ffff.ffff.ffff.ffff.json