rirtracker

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

2a0b:4bc0::/29

Now

RIPE NCC statistics
Allocated (dated 2022-01-28) (RU), in the latest file
Registry
RIPE NCC
Holder
VVT LLC
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2023-05-11 (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.

2023-05-11 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: VPLAB LTD (RIPE NCC) to VVT LLC (RIPE NCC)
From
VPLAB LTD RIPE NCC
To
VVT LLC RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from VPLAB LTD (RIPE NCC) to VVT LLC (RIPE NCC) on 2023-05-11 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 2023-05-11 19:00 UTC, VPLAB LTD (RIPE NCC) to VVT LLC (RIPE NCC); resources moved: 2a0b:4bc0::/29 source · retrieved
  2. Before RIPE NCC delegated statistics 2023-05-10 (produced 2023-05-10T21:59:59+00:00), before the change: allocated (dated 2022-01-28) source · retrieved
  3. After RIPE NCC delegated statistics 2023-05-11 (produced 2023-05-11T21:59:59+00:00), after the change: allocated (dated 2022-01-28) 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
2022-01-28 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
2a0b:4bc0::/29 available on 2022-01-27, allocated on 2022-01-28
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2022-01-27 and allocated (dated 2022-01-28) on 2022-01-28. The tracker saw this range removed from registration on 2021-07-28 (2a0b:4bc0::/32), so it appears to have been issued again from the RIPE NCC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a0b:4bc0::/29 available on 2022-01-27, allocated on 2022-01-28 source · retrieved
  2. Before RIPE NCC delegated statistics 2022-01-27 (produced 2022-01-27T22:59:00+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2022-01-28 (produced 2022-01-28T22:59:00+00:00), after the change: allocated (dated 2022-01-28) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2022-01-24RIPE NCC2a0b:4bc0::/26ReleasedHold released
2021-07-28RIPE NCC2a0b:4bc0::/32− DeregisteredRemoved
2017-06-22RIPE NCC2a0b:4bc0::/32+ RegisteredApparent new issuance

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a0b:4bc0::/29 VPLAB LTD RIPE NCCVVT LLC 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.4bc0..-2a0b.4bc7.ffff.ffff.ffff.ffff.ffff.ffff.json