rirtracker

IPv4 range · 1,024 addresses

2.58.240.0/22

Now

APNIC statistics
Allocated (dated 2019-03-22) (TW), in the latest file
Registry
APNIC
Holder
Not looked up
From
APNIC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of the RIPE NCC

Reported
2024-11-12 (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-11-12 RIPE NCC Transfer log Inter-RIR transfer out of the RIPE NCC Confirmed
Transfer log
Transfer: HostingInside LTD. (RIPE NCC) to (no name) (APNIC)
From
HostingInside LTD. RIPE NCC
To
(no name given) APNIC
Same transfer
APNIC recorded it too: APNIC, 2024-11-12.
Inventory
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants

The RIPE NCC's transfer log records a transfer from HostingInside LTD. (RIPE NCC) to an unnamed organization (APNIC) on 2024-11-12 19:00 UTC: it left the RIPE NCC for APNIC. 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-11-12 19:00 UTC, HostingInside LTD. (RIPE NCC) to (no name) (APNIC); resources moved: 2.58.240.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-11-11 (produced 2024-11-11T22:59:59+00:00), before the change: allocated (dated 2019-03-22) source · retrieved
  3. After RIPE NCC delegated statistics 2024-11-12 (produced 2024-11-12T22: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-11-12 APNIC Transfer log Inter-RIR transfer into APNIC Confirmed
Transfer log
Transfer: ORG-HL197-RIPE (RIPE NCC) to Taiwan Network Information Center/HOSTINGINSIDE (APNIC)
From
ORG-HL197-RIPE RIPE NCC
To
Taiwan Network Information Center/HOSTINGINSIDE APNIC
Same transfer
Also a change at the RIPE NCC, the sending registry: RIPE NCC, 2024-11-12. Lists that cover every registry show it there.
Inventory
Transferred into APNIC administration; not a new issuance

APNIC's transfer log records a transfer from ORG-HL197-RIPE (RIPE NCC) to Taiwan Network Information Center/HOSTINGINSIDE (APNIC) on 2024-11-12 07:12 UTC: it came to APNIC 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-11-12 07:12 UTC, ORG-HL197-RIPE (RIPE NCC) to Taiwan Network Information Center/HOSTINGINSIDE (APNIC); resources moved: 2.58.240.0/22 source · retrieved
  2. Before APNIC delegated statistics 2024-11-12, before the change: not listed source · retrieved
  3. After APNIC delegated statistics 2024-11-13, after the change: allocated (dated 2019-03-22) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into APNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into APNIC, confirmed (classifier 1.4.0) current
2019-03-22 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
2.58.240.0/22 available on 2019-03-21, allocated on 2019-03-22
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2019-03-21 and allocated (dated 2019-03-22) on 2019-03-22. The tracker saw this range released from hold on 2015-03-12 (2.56.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: 2.58.240.0/22 available on 2019-03-21, allocated on 2019-03-22 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-03-21 (produced 2019-03-21T22:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2019-03-22 (produced 2019-03-22T22:59:59+00:00), after the change: allocated (dated 2019-03-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
2015-03-12RIPE NCC2.56.0.0/14ReleasedHold released
2014-03-12RIPE NCC2.58.0.0/15− DeregisteredRemoved
2012-08-07RIPE NCC2.58.0.0/15+ RegisteredApparent reissuance
2012-07-10RIPE NCC2.58.0.0/15− DeregisteredRemoved
2012-06-27RIPE NCC2.58.0.0/15+ RegisteredUnresolved
2012-06-19RIPE NCC2.58.0.0/15− DeregisteredRemoved
2010-09-28RIPE NCC2.56.0.0/14+ RegisteredApparent new issuance

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer2.58.240.0/22 HostingInside LTD. RIPE NCC(no name given) APNIC
APNICResource transfer2.58.240.0/22 ORG-HL197-RIPE RIPE NCCTaiwan Network Information Center/HOSTINGINSIDE APNIC

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/2.58.240.0-2.58.243.255.json