rirtracker

IPv4 range · 1,024 addresses

193.168.176.0/22

Now

RIPE NCC statistics
Allocated (dated 2018-12-11) (RU), in the latest file
Registry
RIPE NCC
Holder
Joint stock company "For"
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2020-12-14 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant 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.

2020-12-14 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: "Uralskie Telekommunikacionnye Seti" Ltd. (RIPE NCC) to Joint stock company "For" (RIPE NCC)
From
"Uralskie Telekommunikacionnye Seti" Ltd. RIPE NCC
To
Joint stock company "For" RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from "Uralskie Telekommunikacionnye Seti" Ltd. (RIPE NCC) to Joint stock company "For" (RIPE NCC) on 2020-12-14 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2020-12-14 19:00 UTC, "Uralskie Telekommunikacionnye Seti" Ltd. (RIPE NCC) to Joint stock company "For" (RIPE NCC); resources moved: 193.168.176.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2020-12-13 (produced 2020-12-13T22:59:00+00:00), before the change: allocated (dated 2018-12-11) source · retrieved
  3. After RIPE NCC delegated statistics 2020-12-14 (produced 2020-12-14T22:59:00+00:00), after the change: allocated (dated 2018-12-11) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
2018-12-11 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
193.168.176.0/22 available on 2018-12-10, allocated on 2018-12-11
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2018-12-10 and allocated (dated 2018-12-11) on 2018-12-11. The tracker saw this range released from hold on 2016-09-07 (193.168.128.0/17), so it appears to have been issued again from the RIPE NCC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 193.168.176.0/22 available on 2018-12-10, allocated on 2018-12-11 source · retrieved
  2. Before RIPE NCC delegated statistics 2018-12-10 (produced 2018-12-10T22:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2018-12-11 (produced 2018-12-11T22:59:59+00:00), after the change: allocated (dated 2018-12-11) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2016-09-07RIPE NCC193.168.128.0/17ReleasedHold released
2016-03-11RIPE NCC193.168.128.0/17− DeregisteredRemoved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer193.168.176.0/22 "Uralskie Telekommunikacionnye Seti" Ltd. RIPE NCCJoint stock company "For" 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/193.168.176.0-193.168.179.255.json