rirtracker

IPv4 range · 512 addresses

209.177.176.0/23

Now

RIPE NCC statistics
Allocated (dated 2008-06-04) (NL), in the latest file
Registry
RIPE NCC
Holder
Teleperformance Netherlands B.V
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Inter-RIR transfer out of ARIN

Reported
2024-07-02 (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.

2024-07-02 ARIN Transfer log Inter-RIR transfer out of ARIN Confirmed
Transfer log
Transfer: TELEPERFORMANCE USA (ARIN) to Teleperformance Netherlands B.V (RIPE NCC)
From
TELEPERFORMANCE USA ARIN
To
Teleperformance Netherlands B.V RIPE NCC
Same transfer
The RIPE NCC recorded it too: RIPE NCC, 2024-07-02.
Piece of
209.177.176.0/20: the rest of the block stayed with the seller
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants

ARIN's transfer log records a transfer from TELEPERFORMANCE USA (ARIN) to Teleperformance Netherlands B.V (RIPE NCC) on 2024-07-02 14:13 UTC: it left ARIN for the RIPE NCC. It is not a new allocation and is not offered to ARIN applicants.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2024-07-02 14:13 UTC, TELEPERFORMANCE USA (ARIN) to Teleperformance Netherlands B.V (RIPE NCC); resources moved: 209.177.176.0/23 source · retrieved
  2. Before ARIN delegated statistics 2024-07-01 (produced 2024-07-01T13:00:44+00:00), before the report: allocated (dated 2008-06-04) source · retrieved
  3. After ARIN delegated statistics 2024-07-03 (produced 2024-07-03T13:00:44+00:00), after the report: not listed source · retrieved
2024-07-02 RIPE NCC Transfer log Inter-RIR transfer into the RIPE NCC Confirmed
Transfer log
Transfer: (no name) (ARIN) to Teleperformance Netherlands B.V (RIPE NCC)
From
(no name given) ARIN
To
Teleperformance Netherlands B.V RIPE NCC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2024-07-02. 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 (ARIN) to Teleperformance Netherlands B.V (RIPE NCC) on 2024-07-02 19:00 UTC: it came to the RIPE NCC 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 2024-07-02 19:00 UTC, (no name) (ARIN) to Teleperformance Netherlands B.V (RIPE NCC); resources moved: 209.177.176.0/23 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-07-01 (produced 2024-07-01T21:59:59+00:00), before the change: not listed source · retrieved
  3. After RIPE NCC delegated statistics 2024-07-02 (produced 2024-07-02T21:59:59+00:00), after the change: allocated (dated 2008-06-04) 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

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2015-05-19ARIN209.177.176.0/20Not in ARIN-IssuedRemoved

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer209.177.176.0/23 (no name given) ARINTeleperformance Netherlands B.V RIPE NCC
ARINResource transfer209.177.176.0/23 TELEPERFORMANCE USA ARINTeleperformance Netherlands B.V 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/209.177.176.0-209.177.177.255.json