rirtracker

IPv4 range · 1,024 addresses

91.196.216.0/22

Now

RIPE NCC statistics
Allocated (dated 2018-06-26) (NL), in the latest file
Registry
RIPE NCC
Holder
HCL Technologies B.V.
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2022-04-01 (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.

2022-04-01 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Beta Teleco S.A.R.L (RIPE NCC) to HCL Technologies B.V. (RIPE NCC)
From
Beta Teleco S.A.R.L RIPE NCC
To
HCL Technologies B.V. RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Beta Teleco S.A.R.L (RIPE NCC) to HCL Technologies B.V. (RIPE NCC) on 2022-04-01 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 2022-04-01 19:00 UTC, Beta Teleco S.A.R.L (RIPE NCC) to HCL Technologies B.V. (RIPE NCC); resources moved: 91.196.216.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2022-03-31 (produced 2022-03-31T21:59:00+00:00), before the change: allocated (dated 2018-06-26) source · retrieved
  3. After RIPE NCC delegated statistics 2022-04-01 (produced 2022-04-01T21:59:00+00:00), after the change: allocated (dated 2018-06-26) 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
2018-06-26 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
91.196.216.0/22 available on 2018-06-25, allocated on 2018-06-26
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2018-06-25 and allocated (dated 2018-06-26) on 2018-06-26. The tracker saw this range removed from registration on 2015-08-14 (91.196.216.0/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: 91.196.216.0/22 available on 2018-06-25, allocated on 2018-06-26 source · retrieved
  2. Before RIPE NCC delegated statistics 2018-06-25 (produced 2018-06-25T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2018-06-26 (produced 2018-06-26T21:59:59+00:00), after the change: allocated (dated 2018-06-26) 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
2015-08-14 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
91.196.216.0/22 assigned on 2015-08-13, reserved on 2015-08-14
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2016-02-10. 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 assigned (dated 2007-06-29) on 2015-08-13 and reserved on 2015-08-14. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2016-02-10. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 91.196.216.0/22 assigned on 2015-08-13, reserved on 2015-08-14 source · retrieved
  2. Before RIPE NCC delegated statistics 2015-08-13 (produced 2015-08-13T21:59:59+00:00), before the change: assigned (dated 2007-06-29) source · retrieved
  3. After RIPE NCC delegated statistics 2015-08-14 (produced 2015-08-14T21: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

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer91.196.216.0/22 Beta Teleco S.A.R.L RIPE NCCHCL Technologies B.V. RIPE NCC

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv4 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/91.196.216.0-91.196.219.255.json