rirtracker

IPv4 range · 1,048,576 addresses

47.0.0.0/12

Now

ARIN statistics
Allocated (dated 2017-11-27), allocated (dated 2019-12-30) (US), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

+ Add Range split/merge or reporting-format change

Reported
2012-02-29 (ARIN)
Confidence
Strong inference
Inventory
No effect on ARIN 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.

2012-02-29 ARIN + Add Range split/merge or reporting-format change Strong inference
ARIN-Issued
Add 47.0.0.0-47.15.255.255
Inventory
No effect on ARIN applicant inventory

This range is part of a larger block from which a piece was transferred around 2012-02-29; the rest was re-registered to show the split. ARIN's statistics show it assigned (dated 1989-01-06) on 2012-02-28 and assigned (dated 2012-02-29) on 2012-03-01. (Until 2013-03-05, ARIN's statistics list only what's issued.)

Evidence (5) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2012-02-29: "Add 47.0.0.0-47.15.255.255" source · retrieved
  2. Before ARIN delegated statistics 2012-02-28, before the report: assigned (dated 1989-01-06) source · retrieved
  3. After ARIN delegated statistics 2012-03-01, after the report: assigned (dated 2012-02-29) source · retrieved
  4. Transfer log Transfer log: RESOURCE_TRANSFER on 2012-02-29 20:24 UTC, Bell-Northern Research (ARIN) to Optimum WiFi (ARIN); resources moved: 47.16.0.0/14 source · retrieved
  5. Transfer log Transfer log: RESOURCE_TRANSFER on 2012-02-29 20:45 UTC, Bell-Northern Research (ARIN) to Optimum WiFi (ARIN); resources moved: 47.20.0.0/14 source · retrieved
Classification history for this change (4 versions)
  1. : Range split/merge or reporting-format change, strong inference (classifier 1.3.0)
  2. : Range split/merge or reporting-format change, strong inference (classifier 1.3.1)
  3. : Range split/merge or reporting-format change, strong inference (classifier 1.3.2)
  4. : Range split/merge or reporting-format change, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2019-12-30ARIN47.10.0.0/16+ AddIntra-ARIN transfer
2017-11-27ARIN47.0.0.0/13+ AddIntra-ARIN transfer
2017-11-27ARIN47.12.0.0 - 47.14.255.255+ AddIntra-ARIN transfer
2016-03-28APNIC47.8.0.0/15Transfer logIntra-APNIC transfer
2016-03-28APNIC47.11.0.0/16Transfer logIntra-APNIC transfer
2016-03-28APNIC47.15.0.0/16Transfer logIntra-APNIC transfer
2016-02-09ARIN47.8.0.0/15Transfer logTransfer out of ARIN
2016-02-09APNIC47.8.0.0/15Transfer logTransfer into APNIC
2016-02-09ARIN47.11.0.0/16Transfer logTransfer out of ARIN
2016-02-09APNIC47.11.0.0/16Transfer logTransfer into APNIC
2016-02-09ARIN47.15.0.0/16Transfer logTransfer out of ARIN
2016-02-09APNIC47.15.0.0/16Transfer logTransfer into APNIC

Transfer records (9)

Date (UTC)LogTypeRange movedFromTo
ARINResource transfer47.10.0.0/16 Bell-Northern Research ARINAmazon Technologies Inc. ARIN
ARINResource transfer47.0.0.0/13 Bell-Northern Research ARINCharter Communications ARIN
ARINResource transfer47.12.0.0/15 Bell-Northern Research ARINCharter Communications ARIN
ARINResource transfer47.14.0.0/16 Bell-Northern Research ARINCharter Communications ARIN
APNICResource transfer47.8.0.0/15 Reliance Jio Infocomm Pte.Ltd APNICReliance Jio Infocomm Limited APNIC
ARINResource transfer47.8.0.0/15 Bell-Northern Research ARINReliance Jio Infocomm Pte Ltd APNIC
ARINResource transfer47.11.0.0/16 Bell-Northern Research ARINReliance Jio Infocomm Pte Ltd APNIC
ARINResource transfer47.15.0.0/16 Bell-Northern Research ARINReliance Jio Infocomm Pte Ltd APNIC
APNICResource transfer47.8.0.0/15 BELLNO ARINReliance Jio Infocomm Pte.Ltd APNIC

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/47.0.0.0-47.15.255.255.json