rirtracker

IPv4 range · 16,384 addresses

5.45.64.0/18

Now

RIPE NCC statistics
Allocated (dated 2012-05-24) (AE, DE, EE), in the latest file
Registry
RIPE NCC
Holder
Not looked up
From
The RIPE NCC's latest statistics

Latest change

+ Registered Apparent reissuance of previously removed resource

Reported
2012-05-24 (RIPE NCC)
Confidence
Strong inference
Inventory
Likely issued from RIPE NCC-controlled 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.

2012-05-24 RIPE NCC + Registered Apparent reissuance of previously removed resource Strong inference
Statistics
5.45.64.0/18 available on 2012-05-23, allocated on 2012-05-24
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2012-05-23 and allocated (dated 2012-05-24) on 2012-05-24. The tracker saw this range removed from registration on 2012-02-22 (5.0.0.0/10), so it appears to have been issued again from the RIPE NCC's pool.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 5.45.64.0/18 available on 2012-05-23, allocated on 2012-05-24 source · retrieved
  2. Before RIPE NCC delegated statistics 2012-05-23 (produced 2012-05-23T21:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2012-05-24 (produced 2012-05-24T21:59:59+00:00), after the change: allocated (dated 2012-05-24) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current

Sold in pieces

2 pieces of this block transferred since 2010-04-23, 62% of it so far.

DatePieceWhat happenedFromTo
2013-04-19 5.45.64.0/19Intra-RIPE NCC transfer Petersburg Internet Network ltd. RIPE NCC3nt solutions LLP RIPE NCC
2013-04-26 5.45.120.0/21Intra-RIPE NCC transfer Petersburg Internet Network ltd. RIPE NCCFASTVPS EESTI OU RIPE NCC

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2025-08-05RIPE NCC5.45.64.0/19Transfer logIntra-RIPE NCC transfer
2019-03-15RIPE NCC5.45.112.0/21Transfer logIntra-RIPE NCC transfer
2019-03-15RIPE NCC5.45.120.0/21Transfer logIntra-RIPE NCC transfer
2013-08-08RIPE NCC5.45.112.0/21Transfer logIntra-RIPE NCC transfer
2013-05-03RIPE NCC5.45.96.0/20Transfer logIntra-RIPE NCC transfer
2013-04-26RIPE NCC5.45.120.0/21Transfer logIntra-RIPE NCC transfer
2013-04-19RIPE NCC5.45.64.0/19Transfer logIntra-RIPE NCC transfer
2012-02-22RIPE NCC5.0.0.0/10− DeregisteredRemoved
2011-03-01RIPE NCC5.0.0.0/10+ RegisteredUnresolved

Transfer records (7)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer5.45.64.0/19 3nt solutions LLP RIPE NCCNetAssets Services - FZCO RIPE NCC
RIPE NCCResource transfer5.45.112.0/21 FASTVPS EESTI OU RIPE NCCP.A.G.M. OU RIPE NCC
RIPE NCCResource transfer5.45.120.0/21 FASTVPS EESTI OU RIPE NCCP.A.G.M. OU RIPE NCC
RIPE NCCResource transfer5.45.112.0/21 Petersburg Internet Network ltd. RIPE NCCFASTVPS EESTI OU RIPE NCC
RIPE NCCResource transfer5.45.96.0/20 Petersburg Internet Network ltd. RIPE NCCnetcup GmbH RIPE NCC
RIPE NCCResource transfer5.45.120.0/21 Petersburg Internet Network ltd. RIPE NCCFASTVPS EESTI OU RIPE NCC
RIPE NCCResource transfer5.45.64.0/19 Petersburg Internet Network ltd. RIPE NCC3nt solutions LLP 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/5.45.64.0-5.45.127.255.json