rirtracker

IPv4 range · 1,024 addresses

5.183.80.0/22

Now

LACNIC statistics
Allocated (dated 2024-07-11) (DO), in the latest file
Registry
LACNIC
Holder
Not looked up
From
LACNIC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of the RIPE NCC

Reported
2024-07-11 (RIPE NCC)
Confidence
Confirmed
Inventory
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants

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.

2024-07-11 RIPE NCC Transfer log Inter-RIR transfer out of the RIPE NCC Confirmed
Transfer log
Transfer: THUNDER NETWORK LIMITED (RIPE NCC) to (no name) (LACNIC)
From
THUNDER NETWORK LIMITED RIPE NCC
To
(no name given) LACNIC
Same transfer
LACNIC recorded it too: LACNIC, 2024-07-11.
Inventory
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants

The RIPE NCC's transfer log records a transfer from THUNDER NETWORK LIMITED (RIPE NCC) to an unnamed organization (LACNIC) on 2024-07-11 19:00 UTC: it left the RIPE NCC for LACNIC. It is not a new allocation and is not offered to RIPE NCC applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-07-11 19:00 UTC, THUNDER NETWORK LIMITED (RIPE NCC) to (no name) (LACNIC); resources moved: 5.183.80.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-07-10 (produced 2024-07-10T21:59:59+00:00), before the change: allocated (dated 2019-04-10) source · retrieved
  3. After RIPE NCC delegated statistics 2024-07-11 (produced 2024-07-11T21:59:59+00:00), after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.4.0) current
2024-07-11 LACNIC Transfer log Inter-RIR transfer into LACNIC Confirmed
Transfer log
Transfer: THUNDER NETWORK LIMITED (RIPE NCC) to COLUMBUS NETWORKS DOMINICANA, S.A. (LACNIC)
From
THUNDER NETWORK LIMITED RIPE NCC
To
COLUMBUS NETWORKS DOMINICANA, S.A. LACNIC
Same transfer
Also a change at the RIPE NCC, the sending registry: RIPE NCC, 2024-07-11. Lists that cover every registry show it there.
Inventory
Transferred into LACNIC administration; not a new issuance

LACNIC's transfer log records a transfer from THUNDER NETWORK LIMITED (RIPE NCC) to COLUMBUS NETWORKS DOMINICANA, S.A. (LACNIC) on 2024-07-11 11:00 UTC: it came to LACNIC from the RIPE NCC. It was already issued by another registry, so this is not a new issuance.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-07-11 11:00 UTC, THUNDER NETWORK LIMITED (RIPE NCC) to COLUMBUS NETWORKS DOMINICANA, S.A. (LACNIC); resources moved: 5.183.80.0/22 source · retrieved
  2. Before LACNIC delegated statistics 2024-07-10, before the change: not listed source · retrieved
  3. After LACNIC delegated statistics 2024-07-11, after the change: allocated (dated 2024-07-11) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.4.0) current
2019-04-10 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
5.183.80.0/22 available on 2019-04-09, allocated on 2019-04-10
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2019-04-09 and allocated (dated 2019-04-10) on 2019-04-10. The tracker saw this range released from hold on 2015-03-12 (5.180.0.0/14), 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: 5.183.80.0/22 available on 2019-04-09, allocated on 2019-04-10 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-04-09 (produced 2019-04-09T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2019-04-10 (produced 2019-04-10T21:59:59+00:00), after the change: allocated (dated 2019-04-10) 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
2015-03-12RIPE NCC5.180.0.0/14ReleasedHold released
2014-03-12RIPE NCC5.180.0.0/14− DeregisteredRemoved
2012-08-07RIPE NCC5.180.0.0/14+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer5.183.80.0/22 THUNDER NETWORK LIMITED RIPE NCC(no name given) LACNIC
LACNICResource transfer5.183.80.0/22 THUNDER NETWORK LIMITED RIPE NCCCOLUMBUS NETWORKS DOMINICANA, S.A. 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/5.183.80.0-5.183.83.255.json