rirtracker

IPv4 range · 2,048 addresses

178.22.24.0/21

Now

RIPE NCC statistics
Allocated (dated 2021-09-02), allocated (dated 2021-09-03) (DE, GB, GE, IT, NL, RU), in the latest file
Registry
RIPE NCC
Holder
Not looked up
From
The RIPE NCC's latest statistics

Latest change

Released Released from hold (the RIPE NCC lists it as 'available')

Reported
2021-05-22 (RIPE NCC)
Confidence
Strong inference
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

Timeline (2)

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.

2021-05-22 RIPE NCC Released Released from hold (the RIPE NCC lists it as 'available') Strong inference
Statistics
178.22.24.0/21 reserved on 2021-05-21, available on 2021-05-22
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

The RIPE NCC's statistics show it reserved on 2021-05-21 and available on 2021-05-22. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2020-11-23, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 178.22.24.0/21 reserved on 2021-05-21, available on 2021-05-22 source · retrieved
  2. Before RIPE NCC delegated statistics 2021-05-21 (produced 2021-05-21T21:59:00+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2021-05-22 (produced 2021-05-22T21:59:00+00:00), after the change: available source · retrieved
Classification history for this change (4 versions)
  1. : Released from hold (the RIPE NCC lists it as 'available'), strong inference (classifier 1.3.0)
  2. : Released from hold (the RIPE NCC lists it as 'available'), strong inference (classifier 1.3.1)
  3. : Released from hold (the RIPE NCC lists it as 'available'), strong inference (classifier 1.3.2)
  4. : Released from hold (the RIPE NCC lists it as 'available'), strong inference (classifier 1.4.0) current
2020-11-23 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
178.22.24.0/21 allocated on 2020-11-22, reserved on 2020-11-23
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2021-05-22. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 2010-03-30) on 2020-11-22 and reserved on 2020-11-23. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2021-05-22. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 178.22.24.0/21 allocated on 2020-11-22, reserved on 2020-11-23 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-11-22 (produced 2020-11-22T22:59:59+00:00), before the change: allocated (dated 2010-03-30) source · retrieved
  3. After RIPE NCC delegated statistics 2020-11-23 (produced 2020-11-23T22:59:59+00:00), 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

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-03-02RIPE NCC178.22.24.0/24Transfer logIntra-RIPE NCC transfer
2025-03-26RIPE NCC178.22.31.0/24Transfer logIntra-RIPE NCC transfer
2023-10-11RIPE NCC178.22.24.0/24Transfer logIntra-RIPE NCC transfer
2021-09-03RIPE NCC178.22.25.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.26.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.27.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.28.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.29.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.30.0/24+ RegisteredApparent reissuance
2021-09-03RIPE NCC178.22.31.0/24+ RegisteredApparent reissuance
2021-09-02RIPE NCC178.22.24.0/24+ RegisteredApparent reissuance

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer178.22.24.0/24 IPX - FZCO RIPE NCCGlobal Communications LLC RIPE NCC
RIPE NCCResource transfer178.22.31.0/24 Galchenko Anna Viktorovna RIPE NCCLLC "Internet Tehnologii" RIPE NCC
RIPE NCCResource transfer178.22.24.0/24 Topline LLC RIPE NCCIPX - FZCO 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/178.22.24.0-178.22.31.255.json