rirtracker

IPv4 range · 8,192 addresses

195.158.192.0/19

Now

RIPE NCC statistics
Allocated (dated 2019-01-16) (DE, GB, RU, SC, UA, US), in the latest file
Registry
RIPE NCC
Holder
Not looked up
From
The RIPE NCC's latest statistics

Latest change

Released Released from hold (the RIPE NCC lists it as 'available')

Reported
2019-01-15 (RIPE NCC)
Confidence
Observed only
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

Timeline (2)

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-01-15 RIPE NCC Released Released from hold (the RIPE NCC lists it as 'available') Observed only
Statistics
195.158.192.0/19 reserved on 2019-01-14, available on 2019-01-15
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

The RIPE NCC's statistics show it reserved on 2019-01-14 and available on 2019-01-15. The RIPE NCC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2018-07-19, 180 days earlier. That is the RIPE NCC's own label: whether and when it is reissued is not confirmed. Another change to this range was reported the day before or after (2019-01-16: Added 195.158.192.0/22; 2019-01-16: Added 195.158.196.0/22; 2019-01-16: Added 195.158.200.0/22), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 195.158.192.0/19 reserved on 2019-01-14, available on 2019-01-15 source · retrieved
  2. Before RIPE NCC delegated statistics 2019-01-14 (produced 2019-01-14T22:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2019-01-15 (produced 2019-01-15T22:59:59+00:00), after the change: available source · retrieved
Classification history for this change (4 versions)
  1. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.0)
  2. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.1)
  3. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.3.2)
  4. : Released from hold (the RIPE NCC lists it as 'available'), observed only (classifier 1.4.0) current
2018-07-19 RIPE NCC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
195.158.192.0/19 allocated on 2018-07-18, reserved on 2018-07-19
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2019-01-15. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it allocated (dated 1997-04-28) on 2018-07-18 and reserved on 2018-07-19. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2019-01-15. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 195.158.192.0/19 allocated on 2018-07-18, reserved on 2018-07-19 source · retrieved
  2. Before RIPE NCC delegated statistics 2018-07-18 (produced 2018-07-18T21:59:59+00:00), before the change: allocated (dated 1997-04-28) source · retrieved
  3. After RIPE NCC delegated statistics 2018-07-19 (produced 2018-07-19T21:59:59+00:00), after the change: reserved source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2024-12-27RIPE NCC195.158.204.0/22Transfer logIntra-RIPE NCC transfer
2023-08-28RIPE NCC195.158.216.0/22Transfer logIntra-RIPE NCC transfer
2022-06-15RIPE NCC195.158.208.0/22Transfer logIntra-RIPE NCC transfer
2021-04-13RIPE NCC195.158.200.0/22Transfer logIntra-RIPE NCC transfer
2021-02-01RIPE NCC195.158.192.0/22Transfer logIntra-RIPE NCC transfer
2019-01-16RIPE NCC195.158.192.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.196.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.200.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.204.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.208.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.212.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.216.0/22+ RegisteredApparent reissuance
2019-01-16RIPE NCC195.158.220.0/22+ RegisteredApparent reissuance

Transfer records (5)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer195.158.204.0/22 Stumpner Netservice UG (haftungsbeschraenkt) RIPE NCCNet1 GmbH RIPE NCC
RIPE NCCResource transfer195.158.216.0/22 Arishi Media Technologies Ltd RIPE NCCNomical Ltd RIPE NCC
RIPE NCCResource transfer195.158.208.0/22 Pawel Damian trading as Backup24 RIPE NCCBedrock Networks LLC RIPE NCC
RIPE NCCResource transfer195.158.200.0/22 EMV Internet Consultants SRL RIPE NCCVodafone Group Services GmbH RIPE NCC
RIPE NCCResource transfer195.158.192.0/22 TeamZen Ltd RIPE NCCRapidSeedbox Ltd 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/195.158.192.0-195.158.223.255.json