rirtracker

IPv4 range · 1,024 addresses

113.212.72.0/22

Now

RIPE NCC statistics
Allocated (dated 2019-06-13) (NL), in the latest file
Registry
RIPE NCC
Holder
ORG-CCB17-RIPE
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of APNIC

Reported
2024-06-11 (APNIC)
Confidence
Confirmed
Inventory
Transferred out of APNIC administration; not offered to APNIC 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-06-11 APNIC Transfer log Inter-RIR transfer out of APNIC Confirmed
Transfer log
Transfer: BMP Australia Group Pty Ltd (APNIC) to ORG-CCB17-RIPE (RIPE NCC)
From
BMP Australia Group Pty Ltd APNIC
To
ORG-CCB17-RIPE RIPE NCC
Same transfer
The RIPE NCC recorded it too: RIPE NCC, 2024-06-10.
Inventory
Transferred out of APNIC administration; not offered to APNIC applicants

APNIC's transfer log records a transfer from BMP Australia Group Pty Ltd (APNIC) to ORG-CCB17-RIPE (RIPE NCC) on 2024-06-10 23:33 UTC: it left APNIC for the RIPE NCC. It is not a new allocation and is not offered to APNIC applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-06-10 23:33 UTC, BMP Australia Group Pty Ltd (APNIC) to ORG-CCB17-RIPE (RIPE NCC); resources moved: 113.212.72.0/22 source · retrieved
  2. Before APNIC delegated statistics 2024-06-11, before the change: allocated (dated 2019-06-13) source · retrieved
  3. After APNIC delegated statistics 2024-06-12, after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of APNIC, confirmed (classifier 1.4.0) current
2024-06-10 RIPE NCC Transfer log Inter-RIR transfer into the RIPE NCC Confirmed
Transfer log
Transfer: (no name) (APNIC) to Critical Core BV (RIPE NCC)
From
(no name given) APNIC
To
Critical Core BV RIPE NCC
Same transfer
Also a change at APNIC, the sending registry: APNIC, 2024-06-11. Lists that cover every registry show it there.
Inventory
Transferred into RIPE NCC administration; not a new issuance

The RIPE NCC's transfer log records a transfer from an unnamed organization (APNIC) to Critical Core BV (RIPE NCC) on 2024-06-10 19:00 UTC: it came to the RIPE NCC from APNIC. 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-06-10 19:00 UTC, (no name) (APNIC) to Critical Core BV (RIPE NCC); resources moved: 113.212.72.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-06-09 (produced 2024-06-09T21:59:59+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2024-06-10 (produced 2024-06-10T21:59:59+00:00), after the change: allocated (dated 2019-06-13) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.4.0) current
2019-06-13 APNIC + Registered Apparent reissuance of previously removed resource Observed only
Statistics
113.212.72.0/22 available on 2019-06-13, allocated on 2019-06-14
Inventory
Likely issued from APNIC-controlled inventory

No transfer record matches. APNIC's statistics show it available on 2019-06-13 and allocated (dated 2019-06-13) on 2019-06-14. The tracker saw this range released from hold on 2019-06-12 (113.212.64.0/19), so it appears to have been issued again from APNIC's pool. Another change to this range was reported the day before or after (2019-06-12: Released 113.212.64.0/19), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 113.212.72.0/22 available on 2019-06-13, allocated on 2019-06-14 source · retrieved
  2. Before APNIC delegated statistics 2019-06-13, before the change: available source · retrieved
  3. After APNIC delegated statistics 2019-06-14, after the change: allocated (dated 2019-06-13) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2019-06-12APNIC113.212.64.0/19ReleasedHold released
2017-05-04APNIC113.212.64.0/19− DeregisteredRemoved
2017-03-02APNIC113.212.64.0/19+ RegisteredRestored
2017-02-01APNIC113.212.64.0/19− DeregisteredRemoved
2008-12-08APNIC113.212.64.0/19+ RegisteredUnresolved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer113.212.72.0/22 BMP Australia Group Pty Ltd APNICORG-CCB17-RIPE RIPE NCC
RIPE NCCResource transfer113.212.72.0/22 (no name given) APNICCritical Core BV 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/113.212.72.0-113.212.75.255.json