rirtracker

IPv4 range · 1,024 addresses

192.140.96.0/22

Now

LACNIC statistics
Allocated (dated 2017-05-08) (BR), in the latest file
Registry
LACNIC
Holder
RV NET TELECOMUNICACOES LTDA
From
LACNIC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-LACNIC transfer

Reported
2024-08-26 (LACNIC)
Confidence
Confirmed
Inventory
No effect on LACNIC 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.

2024-08-26 LACNIC Transfer log Intra-LACNIC transfer Confirmed
Transfer log
Transfer: KBPS TELECOM LTDA (LACNIC) to RV NET TELECOMUNICACOES LTDA (LACNIC)
From
KBPS TELECOM LTDA LACNIC
To
RV NET TELECOMUNICACOES LTDA LACNIC
Inventory
No effect on LACNIC applicant inventory

LACNIC's transfer log records a transfer from KBPS TELECOM LTDA (LACNIC) to RV NET TELECOMUNICACOES LTDA (LACNIC) on 2024-08-26 11:00 UTC. The registration changed hands; it is not a new allocation from LACNIC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-08-26 11:00 UTC, KBPS TELECOM LTDA (LACNIC) to RV NET TELECOMUNICACOES LTDA (LACNIC); resources moved: 192.140.96.0/22 source · retrieved
  2. Before LACNIC delegated statistics 2024-08-25, before the change: allocated (dated 2017-05-08) source · retrieved
  3. After LACNIC delegated statistics 2024-08-26, after the change: allocated (dated 2017-05-08) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-LACNIC transfer, confirmed (classifier 1.3.0)
  2. : Intra-LACNIC transfer, confirmed (classifier 1.3.1)
  3. : Intra-LACNIC transfer, confirmed (classifier 1.3.2)
  4. : Intra-LACNIC transfer, confirmed (classifier 1.4.0) current
2017-05-08 LACNIC + Registered Apparent new issuance Strong inference
Statistics
192.140.96.0/22 reserved on 2017-05-07, allocated on 2017-05-08
Inventory
Likely issued from LACNIC-controlled inventory

No transfer record matches. LACNIC's statistics show it reserved on 2017-05-07 and allocated (dated 2017-05-08) on 2017-05-08. It moved from LACNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by LACNIC.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing LACNIC's daily statistics: 192.140.96.0/22 reserved on 2017-05-07, allocated on 2017-05-08 source · retrieved
  2. Before LACNIC delegated statistics 2017-05-07, before the change: reserved source · retrieved
  3. After LACNIC delegated statistics 2017-05-08, after the change: allocated (dated 2017-05-08) 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 new issuance, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2017-04-05LACNIC192.140.64.0/18ReleasedHold released
2012-05-21RIPE NCC192.140.1.0 - 192.144.73.255− DeregisteredRemoved
2012-03-14RIPE NCC192.140.1.0 - 192.144.73.255+ RegisteredApparent new issuance

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
LACNICResource transfer192.140.96.0/22 KBPS TELECOM LTDA LACNICRV NET TELECOMUNICACOES LTDA LACNIC

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/192.140.96.0-192.140.99.255.json