rirtracker

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

2a03:4100::/29

Now

RIPE NCC statistics
Allocated (dated 2017-04-24) (NL), in the latest file
Registry
RIPE NCC
Holder
Rodin Broadband B.V.
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2021-09-17 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline (3)

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.

2021-09-17 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Rodin Broadband Assetbeheer BV (RIPE NCC) to Rodin Broadband B.V. (RIPE NCC)
From
Rodin Broadband Assetbeheer BV RIPE NCC
To
Rodin Broadband B.V. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Rodin Broadband Assetbeheer BV (RIPE NCC) to Rodin Broadband B.V. (RIPE NCC) on 2021-09-17 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 2021-09-17 19:00 UTC, Rodin Broadband Assetbeheer BV (RIPE NCC) to Rodin Broadband B.V. (RIPE NCC); resources moved: 2a03:4100::/29 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-09-16 (produced 2021-09-16T21:59:00+00:00), before the change: allocated (dated 2017-04-24) source · retrieved
  3. After RIPE NCC delegated statistics 2021-09-17 (produced 2021-09-17T21:59:00+00:00), after the change: allocated (dated 2017-04-24) 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-04-24 RIPE NCC + Registered Apparent reissuance of previously removed resource Observed only
Statistics
2a03:4100::/29 available on 2017-04-23, allocated on 2017-04-24
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2017-04-23 and allocated (dated 2017-04-24) on 2017-04-24. The tracker saw this range removed from registration on 2016-10-25 (2a03:4100::/29), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2017-04-23: Released 2a03:4100::/26), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a03:4100::/29 available on 2017-04-23, allocated on 2017-04-24 source · retrieved
  2. Before RIPE NCC delegated statistics 2017-04-23 (produced 2017-04-23T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2017-04-24 (produced 2017-04-24T21:59:59+00:00), after the change: allocated (dated 2017-04-24) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current
2016-10-25 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a03:4100::/29 allocated on 2016-10-24, reserved on 2016-10-25
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2017-04-23. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2011-03-31) on 2016-10-24 and reserved on 2016-10-25. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv6 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2017-04-23. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a03:4100::/29 allocated on 2016-10-24, reserved on 2016-10-25 source · retrieved
  2. Before RIPE NCC delegated statistics 2016-10-24 (produced 2016-10-24T21:59:59+00:00), before the change: allocated (dated 2011-03-31) source · retrieved
  3. After RIPE NCC delegated statistics 2016-10-25 (produced 2016-10-25T21:59:59+00:00), after the change: reserved source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2017-04-23RIPE NCC2a03:4100::/26ReleasedHold released
2011-04-01RIPE NCC2a03:4100::/32+ RegisteredApparent new issuance

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a03:4100::/29 Rodin Broadband Assetbeheer BV RIPE NCCRodin Broadband B.V. 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/2a03.4100..-2a03.4107.ffff.ffff.ffff.ffff.ffff.ffff.json