rirtracker

IPv4 range · 256 addresses

217.147.55.0/24

Now

RIPE NCC statistics
Allocated (dated 2009-09-24) on 2026-10-09 (DE)
Registry
RIPE NCC
Holder
Stiegeler Internet Service GmbH
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-26 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline since 2026-01-01 (1)

2026-02-26 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Gemeinde Hohentengen am Hochrhein Eb MOKO (RIPE NCC) to Stiegeler Internet Service GmbH (RIPE NCC)
From
Gemeinde Hohentengen am Hochrhein Eb MOKO RIPE NCC
To
Stiegeler Internet Service GmbH RIPE NCC
Piece of
217.147.48.0/20: 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 Gemeinde Hohentengen am Hochrhein Eb MOKO (RIPE NCC) to Stiegeler Internet Service GmbH (RIPE NCC) on 2026-02-26 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-26 19:00 UTC, Gemeinde Hohentengen am Hochrhein Eb MOKO (RIPE NCC) to Stiegeler Internet Service GmbH (RIPE NCC); resources moved: 217.147.55.0/24, 217.147.60.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-02-25 (produced 2026-02-25T22:59:59+00:00), before the change: allocated (dated 2009-09-24) source · retrieved
  3. After RIPE NCC delegated statistics 2026-02-26 (produced 2026-02-26T22:59:59+00:00), after the change: allocated (dated 2009-09-24) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer217.147.55.0/24 Gemeinde Hohentengen am Hochrhein Eb MOKO RIPE NCCStiegeler Internet Service GmbH 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/217.147.55.0-217.147.55.255.json