rirtracker

IPv4 range · 1,024 addresses

182.255.52.0/22

Now

APNIC statistics
Allocated (dated 2016-08-03) (MM), in the latest file
Registry
APNIC
Holder
Not looked up
From
APNIC's latest statistics

Latest change

+ Registered Restored to the same holder

Reported
2023-01-03 (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.

2023-01-03 APNIC + Registered Restored to the same holder Strong inference
Statistics
182.255.52.0/22 reserved on 2023-01-03, allocated on 2023-01-04
Inventory
No effect on APNIC applicant inventory

No transfer record matches. APNIC's statistics show it reserved on 2023-01-03 and allocated (dated 2016-08-03) on 2023-01-04. The tracker saw it removed from registration on 2022-12-22 (12 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: 182.255.52.0/22 reserved on 2023-01-03, allocated on 2023-01-04 source · retrieved
  2. Before APNIC delegated statistics 2023-01-03, before the change: reserved source · retrieved
  3. After APNIC delegated statistics 2023-01-04, after the change: allocated (dated 2016-08-03) 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
2022-12-22 APNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
182.255.52.0/22 allocated on 2022-12-22, reserved on 2022-12-23
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2023-12-22. 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 2016-08-03) on 2022-12-22 and reserved on 2022-12-23. 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 2023-12-22. 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: 182.255.52.0/22 allocated on 2022-12-22, reserved on 2022-12-23 source · retrieved
  2. Before APNIC delegated statistics 2022-12-22, before the change: allocated (dated 2016-08-03) source · retrieved
  3. After APNIC delegated statistics 2022-12-23, 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
2016-08-03 APNIC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
182.255.52.0/22 available on 2016-08-03, allocated on 2016-08-04
Inventory
Likely issued from APNIC-controlled inventory

No transfer record matches. APNIC's statistics show it available on 2016-08-03 and allocated (dated 2016-08-03) on 2016-08-04. The tracker saw this range released from hold on 2016-06-22 (182.255.32.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: 182.255.52.0/22 available on 2016-08-03, allocated on 2016-08-04 source · retrieved
  2. Before APNIC delegated statistics 2016-08-03, before the change: available source · retrieved
  3. After APNIC delegated statistics 2016-08-04, after the change: allocated (dated 2016-08-03) 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
2016-06-22APNIC182.255.32.0/19ReleasedHold released
2015-05-05APNIC182.255.32.0/19− DeregisteredRemoved
2012-10-24APNIC182.255.32.0/19Transfer logIntra-APNIC transfer
2011-03-25APNIC182.255.32.0/19+ RegisteredUnresolved
2011-03-24APNIC182.255.32.0/19− DeregisteredRemoved
2010-05-11APNIC182.255.32.0/19+ RegisteredUnresolved
2009-11-13APNIC182.255.0.0/16− DeregisteredRemoved
2009-08-19APNIC182.255.0.0/16+ RegisteredUnresolved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
APNICResource transfer182.255.32.0/19 Next Web Phil APNICMarbelNetworks 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/182.255.52.0-182.255.55.255.json