rirtracker

IPv4 range · 256 addresses

45.134.243.0/24

Now

RIPE NCC statistics
Reserved on 2026-10-09
Registry
Not known
Holder
Not looked up

Latest change

− Deregistered Removed (return, revocation or reclamation not publicly distinguishable)

Reported
2026-09-14 (RIPE NCC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2026-09-14 (RIPE NCC)
Estimated hold end
Not estimated: RIPE NCC publishes no fixed hold period
Now
Possible reissue candidate; not confirmed available.

Timeline since 2026-01-01 (2)

2026-09-14 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
45.134.243.0/24 allocated on 2026-09-13, reserved on 2026-09-14
Inventory
Possible future reissue candidate after hold

Removed from active registration. The tracker found it by comparing RIPE NCC's daily statistics. RIPE NCC's statistics show it allocated (dated 2026-01-26) on 2026-09-13 and reserved on 2026-09-14. Public sources do not distinguish a voluntary return, revocation, or reclamation. RIPE NCC publishes no fixed period for which it holds returned IPv4 before reissuing them, so the tracker gives no estimate. This does not confirm availability.

Evidence (3) · classifier 1.1.0,
  1. Statistics Found by comparing RIPE NCC's daily statistics: 45.134.243.0/24 allocated on 2026-09-13, reserved on 2026-09-14 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-09-13 (produced 2026-09-13T21:59:59+00:00), before the change: allocated (dated 2026-01-26) source · retrieved
  3. After RIPE NCC delegated statistics 2026-09-14 (produced 2026-09-14T21:59:59+00:00), after the change: reserved source · retrieved
2026-01-26 RIPE NCC + Registered Apparent reissuance of previously removed resource Observed only
Statistics
45.134.243.0/24 available on 2026-01-25, allocated on 2026-01-26
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. RIPE NCC's statistics show it available on 2026-01-25 and allocated (dated 2026-01-26) on 2026-01-26. The tracker saw this range released from hold on 2026-01-25 (45.134.240.0/22), so it appears to have been issued again from RIPE NCC's pool. Another change to this range was reported the day before or after (2026-01-25: Released 45.134.240.0/22), so the before-and-after statistics may include it.

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

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-01-25RIPE NCC45.134.240.0/22ReleasedHold released

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/45.134.243.0-45.134.243.255.json