rirtracker

IPv4 range · 2 prefixes · 8,192 addresses

157.22.176.0 - 157.22.207.255

157.22.176.0/20, 157.22.192.0/20

Now

RIPE NCC statistics
Allocated (dated 1997-10-14) on 2026-10-09 (RU)
Registry
RIPE NCC
Holder
JSC IOT
From
RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-02-04 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-02-04 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Anton Podshibiakin (RIPE NCC) to JSC IOT (RIPE NCC)
From
Anton Podshibiakin RIPE NCC
To
JSC IOT RIPE NCC
Piece of
157.22.0.0 - 157.22.231.255: 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 Anton Podshibiakin (RIPE NCC) to JSC IOT (RIPE NCC) on 2026-02-04 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-02-04 19:00 UTC, Anton Podshibiakin (RIPE NCC) to JSC IOT (RIPE NCC); resources moved: 157.22.176.0 - 157.22.207.255 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-02-03 (produced 2026-02-03T22:59:59+00:00), before the change: assigned (dated 1997-10-14) source · retrieved
  3. After RIPE NCC delegated statistics 2026-02-04 (produced 2026-02-04T22:59:59+00:00), after the change: assigned (dated 1997-10-14) source · retrieved

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer157.22.176.0 - 157.22.207.255 Anton Podshibiakin RIPE NCCJSC IOT RIPE NCC
RIPE NCCResource transfer157.22.0.0/16 (no name given) ARINiNet Ltd RIPE NCC
ARINResource transfer157.22.0.0/16 ViaNet Communications ARINiNet, Ltd 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/157.22.176.0-157.22.207.255.json