rirtracker

IPv4 range · 256 addresses

109.68.222.0/24

Now

RIPE NCC statistics
Allocated (dated 2026-07-13) on 2026-10-09 (AZ)
Registry
RIPE NCC
Holder
Not looked up
From
RIPE NCC's statistics for 2026-10-09

Latest change

+ Registered Apparent reissuance of previously removed resource

Reported
2026-07-13 (RIPE NCC)
Confidence
Strong inference
Inventory
Likely issued from RIPE NCC-controlled inventory

Timeline since 2026-01-01 (1)

2026-07-13 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
109.68.222.0/24 available on 2026-07-12, allocated on 2026-07-13
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. RIPE NCC's statistics show it available on 2026-07-12 and allocated (dated 2026-07-13) on 2026-07-13. The tracker saw this range released from hold on 2026-07-08 (109.68.216.0/21), so it appears to have been issued again from RIPE NCC's pool.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 109.68.222.0/24 available on 2026-07-12, allocated on 2026-07-13 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-07-12 (produced 2026-07-12T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2026-07-13 (produced 2026-07-13T21:59:59+00:00), after the change: allocated (dated 2026-07-13) source · retrieved

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-07-08RIPE NCC109.68.216.0/21ReleasedHold released
2026-01-09RIPE NCC109.68.216.0/21− DeregisteredRemoved

Transfer records

No transfer log has a transfer of any part of this IPv4 range.

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/109.68.222.0-109.68.222.255.json