rirtracker

IPv4 range · 1,024 addresses

46.245.40.0/22

Now

RIPE NCC statistics
Allocated (dated 2010-12-31) on 2026-10-09 (IR)
Registry
RIPE NCC
Holder
Paya Communication Industries (PJSC)
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-08-05 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-08-05 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Hamara System Tabriz Engineering Company (RIPE NCC) to Paya Communication Industries (PJSC) (RIPE NCC)
From
Hamara System Tabriz Engineering Company RIPE NCC
To
Paya Communication Industries (PJSC) RIPE NCC
Piece of
46.245.0.0/18: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Hamara System Tabriz Engineering Company (RIPE NCC) to Paya Communication Industries (PJSC) (RIPE NCC) on 2026-08-05 19:00 UTC. The registration changed hands; it is not a new allocation from RIPE NCC.

Evidence (3) · classifier 1.1.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-08-05 19:00 UTC, Hamara System Tabriz Engineering Company (RIPE NCC) to Paya Communication Industries (PJSC) (RIPE NCC); resources moved: 46.245.40.0/22 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-08-04 (produced 2026-08-04T21:59:59+00:00), before the change: allocated (dated 2010-12-31) source · retrieved
  3. After RIPE NCC delegated statistics 2026-08-05 (produced 2026-08-05T21:59:59+00:00), after the change: allocated (dated 2010-12-31) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer46.245.40.0/22 Hamara System Tabriz Engineering Company RIPE NCCPaya Communication Industries (PJSC) RIPE NCC

Every record in the ARIN and RIPE NCC transfer logs that moved any part of this IPv4 range (ARIN's go back to 2009, the RIPE NCC's to 2012). 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/46.245.40.0-46.245.43.255.json