193.0.232.0/24: registration changes, transfers and evidence

Now

RIPE NCC statistics: Allocated (dated 2023-08-23) on 2026-10-09 (GB)
Registry: RIPE NCC
Holder: Samuel Cosgrove
From: RIPE NCC's statistics for 2026-10-09 and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

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

Timeline since 2026-01-01 (1)

2026-04-13 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed

Transfer log: Transfer: Path Global UK Limited (RIPE NCC) to Samuel Cosgrove (RIPE NCC)
From: Path Global UK Limited RIPE NCC
To: Samuel Cosgrove RIPE NCC
Inventory: No effect on RIPE NCC applicant inventory

RIPE NCC's transfer log records a transfer from Path Global UK Limited (RIPE NCC) to Samuel Cosgrove (RIPE NCC) on 2026-04-13 19:00 UTC. The registration changed hands; it is not a new allocation from RIPE NCC.

Evidence (3) · classifier 1.1.0, 2026-10-10 17:50 UTC

Transfer log Transfer log: RESOURCE_TRANSFER on 2026-04-13 19:00 UTC, Path Global UK Limited (RIPE NCC) to Samuel Cosgrove (RIPE NCC); resources moved: 193.0.232.0/24 source · retrieved 2026-10-10 17:24 UTC
Before RIPE NCC delegated statistics 2026-04-12 (produced 2026-04-12T21:59:59+00:00), before the change: allocated (dated 2023-08-23) source · retrieved 2026-10-10 17:29 UTC
After RIPE NCC delegated statistics 2026-04-13 (produced 2026-04-13T21:59:59+00:00), after the change: allocated (dated 2023-08-23) source · retrieved 2026-10-10 17:30 UTC

Transfer records (1)

Date (UTC)	Log	Type	Range moved	From	To
2026-04-13 19:00 UTC	RIPE NCC	Resource transfer	193.0.232.0/24	Path Global UK Limited RIPE NCC	Samuel Cosgrove RIPE NCC

Date (UTC)

Log

Type

Range moved

From

To

2026-04-13 19:00 UTC

RIPE NCC

Resource transfer

193.0.232.0/24

Path Global UK Limited RIPE NCC

Samuel Cosgrove 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/193.0.232.0-193.0.232.255.json