rirtracker

IPv4 range · 32,768 addresses

101.203.0.0/17

Now

APNIC statistics
Allocated (dated 2011-03-07) (only part of the range) (JP), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

+ Registered Apparent new issuance

Reported
2011-03-07 (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.

2011-03-07 APNIC + Registered Apparent new issuance Strong inference
Statistics
101.203.0.0/17 available on 2011-03-07, allocated on 2011-03-08
Inventory
Likely issued from APNIC-controlled inventory

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

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 101.203.0.0/17 available on 2011-03-07, allocated on 2011-03-08 source · retrieved
  2. Before APNIC delegated statistics 2011-03-07, before the change: available source · retrieved
  3. After APNIC delegated statistics 2011-03-08, after the change: allocated (dated 2011-03-07) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent new issuance, strong inference (classifier 1.3.0)
  2. : Apparent new issuance, strong inference (classifier 1.3.1)
  3. : Apparent new issuance, strong inference (classifier 1.3.2)
  4. : Apparent new issuance, strong inference (classifier 1.4.0) current

Sold in pieces

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

DatePieceWhat happenedFromTo
2019-12-03 101.203.64.0/18Intra-APNIC transfer Japan Network Information Center/eAccess APNICJapan Network Information Center/BBIXINTLNET APNIC
2020-11-05 101.203.84.0/23Transfer out of APNIC Japan Network Information Center/BBIXINTLNET APNICBU-231 ARIN
2023-03-15 101.203.0.0/19Intra-APNIC transfer Japan Network Information Center/BBIXINTLNET APNICJapan Network Information Center/ncv APNIC
2023-03-15 101.203.32.0/20Intra-APNIC transfer Japan Network Information Center/BBIXINTLNET APNICJapan Network Information Center/ncv APNIC

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2023-03-15APNIC101.203.0.0/19Transfer logIntra-APNIC transfer
2023-03-15APNIC101.203.32.0/20Transfer logIntra-APNIC transfer
2023-02-15APNIC101.203.0.0/18Transfer logIntra-APNIC transfer
2020-11-05APNIC101.203.84.0/23Transfer logTransfer out of APNIC
2020-11-04ARIN101.203.84.0/23+ AddTransfer into ARIN
2019-12-03APNIC101.203.64.0/18Transfer logIntra-APNIC transfer

Transfer records (5)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer101.203.0.0/19 Japan Network Information Center/BBIXINTLNET APNICJapan Network Information Center/ncv APNIC
APNICResource transfer101.203.0.0/18 Japan Network Information Center/eaccess APNICJapan Network Information Center/BBIXINTLNET APNIC
APNICResource transfer101.203.84.0/23 Japan Network Information Center/BBIXINTLNET APNICBU-231 ARIN
ARINResource transfer101.203.84.0/23 BBIX International, Inc. APNICBBIX USA, INC. ARIN
APNICResource transfer101.203.64.0/18 Japan Network Information Center/eAccess APNICJapan Network Information Center/BBIXINTLNET 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/101.203.0.0-101.203.127.255.json