rirtracker

IPv4 range · 256 addresses

188.119.155.0/24

Now

RIPE NCC statistics
Allocated (dated 2009-07-06) on 2026-10-09 (GB)
Registry
RIPE NCC
Holder
Host Media Ltd
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-18 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-02-18 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: ESSENSYS (UK) Ltd. (RIPE NCC) to Host Media Ltd (RIPE NCC)
From
ESSENSYS (UK) Ltd. RIPE NCC
To
Host Media Ltd RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from ESSENSYS (UK) Ltd. (RIPE NCC) to Host Media Ltd (RIPE NCC) on 2026-02-18 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-18 19:00 UTC, ESSENSYS (UK) Ltd. (RIPE NCC) to Host Media Ltd (RIPE NCC); resources moved: 188.119.155.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-02-17 (produced 2026-02-17T22:59:59+00:00), before the change: allocated (dated 2009-07-06) source · retrieved
  3. After RIPE NCC delegated statistics 2026-02-18 (produced 2026-02-18T22:59:59+00:00), after the change: allocated (dated 2009-07-06) source · retrieved

Transfer records (4)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer188.119.155.0/24 ESSENSYS (UK) Ltd. RIPE NCCHost Media Ltd RIPE NCC
RIPE NCCResource transfer188.119.155.0/24 NAV COMMUNICATIONS SRL RIPE NCCessensys Ltd RIPE NCC
RIPE NCCResource transfer188.119.152.0/22 NAV DATACENTER TELECOM SRL RIPE NCCHOSTING MEDIA SRL RIPE NCC
RIPE NCCResource transfer188.119.152.0/22 SC RoSite Equipment SRL RIPE NCCNAV DATACENTER TELECOM SRL 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/188.119.155.0-188.119.155.255.json