rirtracker

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

2a07:e000::/29

Now

RIPE NCC statistics
Allocated (dated 2020-05-04) (EE), in the latest file
Registry
RIPE NCC
Holder
LIRBEE OU
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2025-12-29 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline (5)

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.

2025-12-29 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: MYWEB LIMITED (RIPE NCC) to LIRBEE OU (RIPE NCC)
From
MYWEB LIMITED RIPE NCC
To
LIRBEE OU RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from MYWEB LIMITED (RIPE NCC) to LIRBEE OU (RIPE NCC) on 2025-12-29 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 2025-12-29 19:00 UTC, MYWEB LIMITED (RIPE NCC) to LIRBEE OU (RIPE NCC); resources moved: 2a07:e000::/29 source · retrieved
  2. Before RIPE NCC delegated statistics 2025-12-28 (produced 2025-12-28T22:59:59+00:00), before the change: allocated (dated 2020-05-04) source · retrieved
  3. After RIPE NCC delegated statistics 2025-12-29 (produced 2025-12-29T22:59:59+00:00), after the change: allocated (dated 2020-05-04) 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
2021-09-03 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Vikas Saini Trading as ZUMY COMMUNICATIONS (RIPE NCC) to MYWEB LIMITED (RIPE NCC)
From
Vikas Saini Trading as ZUMY COMMUNICATIONS RIPE NCC
To
MYWEB LIMITED RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Vikas Saini Trading as ZUMY COMMUNICATIONS (RIPE NCC) to MYWEB LIMITED (RIPE NCC) on 2021-09-03 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-03 19:00 UTC, Vikas Saini Trading as ZUMY COMMUNICATIONS (RIPE NCC) to MYWEB LIMITED (RIPE NCC); resources moved: 2a07:e000::/29 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-09-02 (produced 2021-09-02T21:59:00+00:00), before the change: allocated (dated 2020-05-04) source · retrieved
  3. After RIPE NCC delegated statistics 2021-09-03 (produced 2021-09-03T21:59:00+00:00), after the change: allocated (dated 2020-05-04) 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
2020-05-04 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
2a07:e000::/29 available on 2020-05-03, allocated on 2020-05-04
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2020-05-03 and allocated (dated 2020-05-04) on 2020-05-04. The tracker saw this range removed from registration on 2019-11-04 (2a07:e000::/29), 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: 2a07:e000::/29 available on 2020-05-03, allocated on 2020-05-04 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-05-03 (produced 2020-05-03T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2020-05-04 (produced 2020-05-04T21:59:59+00:00), after the change: allocated (dated 2020-05-04) 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
2019-11-04 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
2a07:e000::/29 allocated on 2019-11-03, reserved on 2019-11-04
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2020-05-02. 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 2018-05-22) on 2019-11-03 and reserved on 2019-11-04. 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 2020-05-02. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a07:e000::/29 allocated on 2019-11-03, reserved on 2019-11-04 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-11-03 (produced 2019-11-03T22:59:59+00:00), before the change: allocated (dated 2018-05-22) source · retrieved
  3. After RIPE NCC delegated statistics 2019-11-04 (produced 2019-11-04T22: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
2018-05-22 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
2a07:e000::/29 available on 2018-05-21, allocated on 2018-05-22
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2018-05-21 and allocated (dated 2018-05-22) on 2018-05-22. The tracker saw this range removed from registration on 2017-12-22 (2a07:e000::/22), 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: 2a07:e000::/29 available on 2018-05-21, allocated on 2018-05-22 source · retrieved
  2. Before RIPE NCC delegated statistics 2018-05-21 (produced 2018-05-21T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2018-05-22 (produced 2018-05-22T21:59:59+00:00), after the change: allocated (dated 2018-05-22) 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
2020-05-02RIPE NCC2a07:e000::/25ReleasedHold released
2018-03-13RIPE NCC2a07:e000::/19ReleasedHold released
2017-12-29RIPE NCC2a07:e000::/19ReleasedHold released
2017-12-22RIPE NCC2a07:e000::/22− DeregisteredRemoved
2017-12-21RIPE NCC2a07:e000::/22+ RegisteredApparent new issuance
2015-03-25RIPE NCC2a06::/15ReleasedRIPE NCC pool record

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2a07:e000::/29 MYWEB LIMITED RIPE NCCLIRBEE OU RIPE NCC
RIPE NCCResource transfer2a07:e000::/29 Vikas Saini Trading as ZUMY COMMUNICATIONS RIPE NCCMYWEB LIMITED 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/2a07.e000..-2a07.e007.ffff.ffff.ffff.ffff.ffff.ffff.json