rirtracker

IPv4 range · 4,096 addresses

190.106.64.0/20

Now

RIPE NCC statistics
Allocated (dated 2008-11-28) (NL), in the latest file
Registry
RIPE NCC
Holder
Nimbus IP Networks BV
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer into the RIPE NCC

Reported
2024-09-12 (RIPE NCC)
Confidence
Confirmed
Inventory
Transferred into RIPE NCC administration; not a new issuance

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.

2024-09-12 RIPE NCC Transfer log Inter-RIR transfer into the RIPE NCC Confirmed
Transfer log
Transfer: (no name) (LACNIC) to Nimbus IP Networks BV (RIPE NCC)
From
(no name given) LACNIC
To
Nimbus IP Networks BV RIPE NCC
Same transfer
Also a change at LACNIC, the sending registry: LACNIC, 2024-09-12. Lists that cover every registry show it there.
Inventory
Transferred into RIPE NCC administration; not a new issuance

The RIPE NCC's transfer log records a transfer from an unnamed organization (LACNIC) to Nimbus IP Networks BV (RIPE NCC) on 2024-09-12 19:00 UTC: it came to the RIPE NCC from LACNIC. It was already issued by another registry, so this is not a new issuance.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-09-12 19:00 UTC, (no name) (LACNIC) to Nimbus IP Networks BV (RIPE NCC); resources moved: 190.106.64.0/20 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-09-11 (produced 2024-09-11T21:59:59+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2024-09-12 (produced 2024-09-12T21:59:59+00:00), after the change: allocated (dated 2008-11-28) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into the RIPE NCC, confirmed (classifier 1.4.0) current
2024-09-12 LACNIC Transfer log Inter-RIR transfer out of LACNIC Confirmed
Transfer log
Transfer: CRISP S.A. (LACNIC) to Nimbus IP Networks BV (RIPE NCC)
From
CRISP S.A. LACNIC
To
Nimbus IP Networks BV RIPE NCC
Same transfer
The RIPE NCC recorded it too: RIPE NCC, 2024-09-12.
Inventory
Transferred out of LACNIC administration; not offered to LACNIC applicants

LACNIC's transfer log records a transfer from CRISP S.A. (LACNIC) to Nimbus IP Networks BV (RIPE NCC) on 2024-09-12 11:00 UTC: it left LACNIC for the RIPE NCC. It is not a new allocation and is not offered to LACNIC applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-09-12 11:00 UTC, CRISP S.A. (LACNIC) to Nimbus IP Networks BV (RIPE NCC); resources moved: 190.106.64.0/20 source · retrieved
  2. Before LACNIC delegated statistics 2024-09-11, before the change: allocated (dated 2008-11-28) source · retrieved
  3. After LACNIC delegated statistics 2024-09-12, after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of LACNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of LACNIC, confirmed (classifier 1.4.0) current

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer190.106.64.0/20 (no name given) LACNICNimbus IP Networks BV RIPE NCC
LACNICResource transfer190.106.64.0/20 CRISP S.A. LACNICNimbus IP Networks BV 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/190.106.64.0-190.106.79.255.json