rirtracker

IPv4 range · 1,024 addresses

202.160.136.0/22

Now

APNIC statistics
Allocated (dated 2015-12-08) (ID), in the latest file
Registry
APNIC
Holder
Not looked up
From
APNIC's latest statistics

Latest change

+ Registered Apparent reissuance of previously removed resource

Reported
2015-12-08 (APNIC)
Confidence
Strong inference
Inventory
Likely issued from APNIC-controlled inventory

Timeline (1)

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.

2015-12-08 APNIC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
202.160.136.0/22 available on 2015-12-08, allocated on 2015-12-09
Inventory
Likely issued from APNIC-controlled inventory

No transfer record matches. APNIC's statistics show it available on 2015-12-08 and allocated (dated 2015-12-08) on 2015-12-09. The tracker saw this range released from hold on 2015-10-28 (202.160.128.0/19), so it appears to have been issued again from APNIC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 202.160.136.0/22 available on 2015-12-08, allocated on 2015-12-09 source · retrieved
  2. Before APNIC delegated statistics 2015-12-08, before the change: available source · retrieved
  3. After APNIC delegated statistics 2015-12-09, after the change: allocated (dated 2015-12-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 reissuance of previously removed resource, strong inference (classifier 1.4.0) current

Sold in pieces

2 pieces of this block transferred since 2008-02-15, 75% of it so far.

DatePieceWhat happenedFromTo
2023-03-28 202.160.136.0/23Intra-APNIC transfer Indonesia Network Information Center/VELTRA-ID APNICIndonesia Network Information Center/ATSINDO-ID APNIC
2023-03-28 202.160.138.0/24Intra-APNIC transfer Indonesia Network Information Center/VELTRA-ID APNICIndonesia Network Information Center/ATSINDO-ID APNIC

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-03-27APNIC202.160.139.0/24Transfer logIntra-APNIC transfer
2023-03-28APNIC202.160.136.0/23Transfer logIntra-APNIC transfer
2023-03-28APNIC202.160.138.0/24Transfer logIntra-APNIC transfer
2015-10-28APNIC202.160.128.0/19ReleasedHold released
2011-04-29APNIC202.160.128.0/19− DeregisteredRemoved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer202.160.139.0/24 Indonesia Network Information Center/VELTRA-ID APNICIndonesia Network Information Center/IDNIC-DASARATA-ID APNIC
APNICResource transfer202.160.136.0/23 Indonesia Network Information Center/VELTRA-ID APNICIndonesia Network Information Center/ATSINDO-ID 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/202.160.136.0-202.160.139.255.json