rirtracker

IPv4 range · 2,048 addresses

88.133.232.0/21

Now

RIPE NCC statistics
Allocated (dated 2005-10-28) (DE), in the latest file
Registry
RIPE NCC
Holder
R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG
From
The RIPE NCC's latest statistics and the latest transfer record

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2019-05-03 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

Timeline (1)

Every change the tracker has found, newest first. It covers ARIN from 2008-12-01, the RIPE NCC from 2010-04-23, APNIC from 2008-02-15, LACNIC from 2012-06-29 and AFRINIC from 2012-10-03.

2019-05-03 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as G-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH & Co. KG (RIPE NCC) to R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG (RIPE NCC)
From
R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as G-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH & Co. KG RIPE NCC
To
R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG RIPE NCC
Piece of
88.133.0.0/16: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as G-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH & Co. KG (RIPE NCC) to R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG (RIPE NCC) on 2019-05-03 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2019-05-03 19:00 UTC, R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as G-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH & Co. KG (RIPE NCC) to R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG (RIPE NCC); resources moved: 88.133.232.0/21 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-05-02 (produced 2019-05-02T21:59:59+00:00), before the change: allocated (dated 2005-10-28) source · retrieved
  3. After RIPE NCC delegated statistics 2019-05-03 (produced 2019-05-03T21:59:59+00:00), after the change: allocated (dated 2005-10-28) source · retrieved
Classification history for this change (4 versions)
  1. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.0)
  2. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.1)
  3. : Intra-RIPE NCC transfer, confirmed (classifier 1.3.2)
  4. : Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2014-10-15RIPE NCC88.133.224.0/19Transfer logIntra-RIPE NCC transfer

Transfer records (2)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer88.133.232.0/21 R-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as G-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH & Co. KG RIPE NCCR-KOM Regensburger Telekommunikationsverwaltungsgesellschaft mbH trading as R-KOM Regensburger Telekommunikationsgesellschaft mbH & Co. KG RIPE NCC
RIPE NCCResource transfer88.133.224.0/19 Televersa Online GmbH RIPE NCCG-FIT Gesellschaft fuer innovative Telekommunikationsdienste mbH Co. KG RIPE NCC

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv4 range (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). 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/88.133.232.0-88.133.239.255.json