rirtracker

IPv4 range · 4,096 addresses

149.19.160.0/20

Now

LACNIC statistics
Allocated (dated 2021-04-05) (CL), in the latest file
Registry
LACNIC
Holder
Starlink Chile SpA
From
LACNIC's latest statistics and the latest transfer record

Latest change

Not in ARIN-Issued Inter-RIR transfer out of ARIN

Reported
2021-04-05 (ARIN)
Confidence
Confirmed
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

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-04-05 ARIN Not in ARIN-Issued Inter-RIR transfer out of ARIN Confirmed
From
CMA Consulting Services ARIN
To
Starlink Chile SpA LACNIC
Same transfer
LACNIC recorded it too: LACNIC, 2021-04-05.
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

ARIN's transfer log records a transfer from CMA Consulting Services (ARIN) to Starlink Chile SpA (LACNIC) on 2021-04-05 14:23 UTC: it left ARIN for LACNIC. ARIN-Issued didn't list this change; it is not a new allocation and is not offered to ARIN applicants.

Evidence (4) · classifier 1.4.0,
  1. Statistics Not listed in ARIN-Issued; found by comparing ARIN's daily statistics: 149.19.160.0/20 assigned on 2021-04-05, not listed on 2021-04-06 source · retrieved
  2. Transfer log Transfer log: RESOURCE_TRANSFER on 2021-04-05 14:23 UTC, CMA Consulting Services (ARIN) to Starlink Chile SpA (LACNIC); resources moved: 149.19.160.0/20 source · retrieved
  3. Before ARIN delegated statistics 2021-04-04 (produced 2021-04-04T14:00:13+00:00), before the report: assigned (dated 1993-06-01) source · retrieved
  4. After ARIN delegated statistics 2021-04-06 (produced 2021-04-06T14:00:13+00:00), after the report: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer out of ARIN, confirmed (classifier 1.4.0) current
2021-04-05 LACNIC Transfer log Inter-RIR transfer into LACNIC Confirmed
Transfer log
Transfer: CMA Consulting Services (ARIN) to STARLINK CHILE SPA (LACNIC)
From
CMA Consulting Services ARIN
To
STARLINK CHILE SPA LACNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2021-04-05. Lists that cover every registry show it there.
Inventory
Transferred into LACNIC administration; not a new issuance

LACNIC's transfer log records a transfer from CMA Consulting Services (ARIN) to STARLINK CHILE SPA (LACNIC) on 2021-04-05 11:00 UTC: it came to LACNIC from ARIN. 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 2021-04-05 11:00 UTC, CMA Consulting Services (ARIN) to STARLINK CHILE SPA (LACNIC); resources moved: 149.19.160.0/20 source · retrieved
  2. Before LACNIC delegated statistics 2021-04-04, before the change: not listed source · retrieved
  3. After LACNIC delegated statistics 2021-04-05, after the change: allocated (dated 2021-04-05) source · retrieved
Classification history for this change (4 versions)
  1. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.0)
  2. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.1)
  3. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.3.2)
  4. : Inter-RIR transfer into LACNIC, confirmed (classifier 1.4.0) current

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
ARINResource transfer149.19.160.0/20 CMA Consulting Services ARINStarlink Chile SpA LACNIC
LACNICResource transfer149.19.160.0/20 CMA Consulting Services ARINSTARLINK CHILE SPA LACNIC

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/149.19.160.0-149.19.175.255.json