rirtracker

IPv4 range · 1,024 addresses

103.228.0.0/22

Now

APNIC statistics
Allocated (dated 2014-03-20) (only part of the range) (BD), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

+ Registered Restored to the same holder

Reported
2019-10-18 (APNIC)
Confidence
Strong inference
Inventory
No effect on APNIC applicant inventory

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.

2019-10-18 APNIC + Registered Restored to the same holder Strong inference
Statistics
103.228.0.0/22 reserved on 2019-10-18, allocated on 2019-10-19
Inventory
No effect on APNIC applicant inventory

No transfer record matches. APNIC's statistics show it reserved on 2019-10-18 and allocated (dated 2014-03-20) on 2019-10-19. The tracker saw it removed from registration on 2019-10-10 (8 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 103.228.0.0/22 reserved on 2019-10-18, allocated on 2019-10-19 source · retrieved
  2. Before APNIC delegated statistics 2019-10-18, before the change: reserved source · retrieved
  3. After APNIC delegated statistics 2019-10-19, after the change: allocated (dated 2014-03-20) source · retrieved
Classification history for this change (4 versions)
  1. : Restored to the same holder, strong inference (classifier 1.3.0)
  2. : Restored to the same holder, strong inference (classifier 1.3.1)
  3. : Restored to the same holder, strong inference (classifier 1.3.2)
  4. : Restored to the same holder, strong inference (classifier 1.4.0) current
2019-10-10 APNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
103.228.0.0/22 allocated on 2019-10-10, reserved on 2019-10-11
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2020-10-10. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2014-03-20) on 2019-10-10 and reserved on 2019-10-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2020-10-10. That is what APNIC has done, not a rule it states. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 103.228.0.0/22 allocated on 2019-10-10, reserved on 2019-10-11 source · retrieved
  2. Before APNIC delegated statistics 2019-10-10, before the change: allocated (dated 2014-03-20) source · retrieved
  3. After APNIC delegated statistics 2019-10-11, after the change: reserved source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2014-03-20 APNIC + Registered Apparent new issuance Strong inference
Statistics
103.228.0.0/22 available on 2014-03-20, allocated on 2014-03-21
Inventory
Likely issued from APNIC-controlled inventory

No transfer record matches. APNIC's statistics show it available on 2014-03-20 and allocated (dated 2014-03-20) on 2014-03-21. 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: 103.228.0.0/22 available on 2014-03-20, allocated on 2014-03-21 source · retrieved
  2. Before APNIC delegated statistics 2014-03-20, before the change: available source · retrieved
  3. After APNIC delegated statistics 2014-03-21, after the change: allocated (dated 2014-03-20) 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

1 piece of this block transferred since 2008-02-15, 25% of it so far.

DatePieceWhat happenedFromTo
2024-03-05 103.228.3.0/24Transfer out of APNIC Ashraful Alam APNICORG-TCDS1-RIPE RIPE NCC

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2024-06-12APNIC103.228.2.0/24Transfer logTransfer out of APNIC
2024-06-10RIPE NCC103.228.2.0/24Transfer logTransfer into the RIPE NCC
2024-03-05APNIC103.228.3.0/24Transfer logTransfer out of APNIC
2024-03-04RIPE NCC103.228.3.0/24Transfer logTransfer into the RIPE NCC

Transfer records (4)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer103.228.2.0/24 Ashraful Alam APNICORG-NL415-RIPE RIPE NCC
RIPE NCCResource transfer103.228.2.0/24 (no name given) APNICNavant LLC RIPE NCC
RIPE NCCResource transfer103.228.3.0/24 (no name given) APNICTelevision Cable Digital S.L. RIPE NCC
APNICResource transfer103.228.3.0/24 Ashraful Alam APNICORG-TCDS1-RIPE 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/103.228.0.0-103.228.3.255.json