rirtracker

IPv4 range · 1,024 addresses

213.170.212.0/22

Now

RIPE NCC statistics
Allocated (dated 2019-05-06) (CH), in the latest file
Registry
RIPE NCC
Holder
Not looked up
From
The RIPE NCC's latest statistics

Latest change

+ Registered Apparent reissuance of previously removed resource

Reported
2019-05-06 (RIPE NCC)
Confidence
Observed only
Inventory
Likely issued from RIPE NCC-controlled inventory

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.

2019-05-06 RIPE NCC + Registered Apparent reissuance of previously removed resource Observed only
Statistics
213.170.212.0/22 available on 2019-05-05, allocated on 2019-05-06
Inventory
Likely issued from RIPE NCC-controlled inventory

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

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 213.170.212.0/22 available on 2019-05-05, allocated on 2019-05-06 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-05-05 (produced 2019-05-05T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2019-05-06 (produced 2019-05-06T21:59:59+00:00), after the change: allocated (dated 2019-05-06) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current
2019-05-05 RIPE NCC Released Released from hold (the RIPE NCC lists it as 'available') Observed only
Statistics
213.170.212.0/22 reserved on 2019-05-04, available on 2019-05-05
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

The RIPE NCC's statistics show it reserved on 2019-05-04 and available on 2019-05-05. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed. Another change to this range was reported the day before or after (2019-05-06: Added 213.170.212.0/22), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 213.170.212.0/22 reserved on 2019-05-04, available on 2019-05-05 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-05-04 (produced 2019-05-04T21:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2019-05-05 (produced 2019-05-05T21:59:59+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'), observed only (classifier 1.3.0)
  2. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.1)
  3. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.2)
  4. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2014-07-02RIPE NCC213.170.192.0/19ReleasedHold released
2013-07-02RIPE NCC213.170.192.0/19− 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/213.170.212.0-213.170.215.255.json