rirtracker

IPv4 range · 1,024 addresses

188.209.116.0/22

Now

RIPE NCC statistics
Allocated (dated 2009-05-08) (IR), in the latest file
Registry
RIPE NCC
Holder
Fannavaran-e Idea Pardaz-e Saba PJSC
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2022-05-03 (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.

2022-05-03 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Padidar Technology Co (RIPE NCC) to Fannavaran-e Idea Pardaz-e Saba PJSC (RIPE NCC)
From
Padidar Technology Co RIPE NCC
To
Fannavaran-e Idea Pardaz-e Saba PJSC RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Padidar Technology Co (RIPE NCC) to Fannavaran-e Idea Pardaz-e Saba PJSC (RIPE NCC) on 2022-05-03 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 2022-05-03 19:00 UTC, Padidar Technology Co (RIPE NCC) to Fannavaran-e Idea Pardaz-e Saba PJSC (RIPE NCC); resources moved: 188.209.116.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2022-05-02 (produced 2022-05-02T21:59:00+00:00), before the change: allocated (dated 2009-05-08) source · retrieved
  3. After RIPE NCC delegated statistics 2022-05-03 (produced 2022-05-03T21:59:00+00:00), after the change: allocated (dated 2009-05-08) 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
2015-08-11 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Jump Management SRL (RIPE NCC) to Padidar Technology Co (RIPE NCC)
From
Jump Management SRL RIPE NCC
To
Padidar Technology Co RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Jump Management SRL (RIPE NCC) to Padidar Technology Co (RIPE NCC) on 2015-08-11 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 2015-08-11 19:00 UTC, Jump Management SRL (RIPE NCC) to Padidar Technology Co (RIPE NCC); resources moved: 188.209.116.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2015-08-10 (produced 2015-08-10T21:59:59+00:00), before the change: allocated (dated 2009-05-08) source · retrieved
  3. After RIPE NCC delegated statistics 2015-08-11 (produced 2015-08-11T21:59:59+00:00), after the change: allocated (dated 2009-05-08) 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

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer188.209.116.0/22 Padidar Technology Co RIPE NCCFannavaran-e Idea Pardaz-e Saba PJSC RIPE NCC
RIPE NCCResource transfer188.209.116.0/22 Jump Management SRL RIPE NCCPadidar Technology Co 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/188.209.116.0-188.209.119.255.json