Summary
- The 3 November APNIC original carried two Bangladesh-coded, 512-address IPv4 allocations:
103.7.4.0/23dated 16 September 2022 and163.227.238.0/23dated 5 May 2025. - The 4 November original keeps the first /24 of each as allocated and puts
103.7.5.0/24and163.227.239.0/24in reserve. The two old /23s account for 1,024 addresses; 512 remain allocated and 512 are reserved.
Take the first row literally. On 3 November APNIC listed 103.7.4.0 with a count of 512, Bangladesh country code, an allocated status, the 2022 date and holder identifier A914661C. One daily file later, 103.7.4.0 has a count of 256 with the same date and identifier. Its adjacent 256 addresses, beginning at 103.7.5.0, appear separately as reserved, with no country, date or holder identifier. The second pair follows the same arithmetic: 163.227.238.0 falls from 512 allocated addresses to 256, while the adjacent 163.227.239.0/24 becomes reserved. Its surviving allocation retains its own identifier, A918E269, and its 2025 date. These are two separate account identifiers, not one combined transaction.
The exact RDAP record for 103.7.4.0/24 names HPLINKINTERNET-BD; the record for 163.227.238.0/24 names SERVER-BD. Both are active, Bangladesh-coded, exact /24 objects. Their registration events are on 3 November at 05:04:01 and 04:55:44 UTC respectively. Those timestamps date the current objects. They do not date the old /23 allocations, whose dates survive in the statistical rows.
Ask RDAP about the two reserved halves and the answer widens sharply. The 103.7.5.0/24 query returns an APNIC administrative record spanning the entire 103.0.0.0/8. The 163.227.239.0/24 query returns an administrative record for 163.0.0.0/8. Neither is an exact holder card for the reserved /24. The daily file supplies the precise reserved range; RDAP supplies a holder-specific card only for each continuing allocated half.
APNIC's address-status guide gives these columns different jobs. Allocated belongs to a delegated account-holding organisation. Reserved is a separate state within APNIC's pool; its guide describes quarantine among the uses of reserve. The two daily files give no case reason for either half-reserve; a dated resource-action record for each pair would establish it.
The file headers keep the chronology straight. The 3 November file reports data through 2 November; the 4 November file reports data through 3 November. A 2022 or 2025 allocation date left on a surviving /24 is history attached to that half, not proof that the original /23 still occupies the allocated column. That is the trap in a spreadsheet that looks reassuring because the date did not move.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance





