rirtracker

IPv6 range · 20,282,409,603,651,670,423,947,251,286,016 addresses

2a04:fe00::/24

Now

RIPE NCC statistics
Allocated (dated 2015-04-09), allocated (dated 2015-05-07), allocated (dated 2020-05-07), available, reserved (AE, DK, GB, RO), in the latest file
Registry
Not known
Holder
Not looked up

Latest change

Released Change to the RIPE NCC's own pool record

Reported
2015-03-25 (RIPE NCC)
Confidence
Strong inference
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

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.

2015-03-25 RIPE NCC Released Change to the RIPE NCC's own pool record Strong inference
Statistics
2a04:fe00::/24 reserved on 2015-03-24, available on 2015-03-25
Inventory
The RIPE NCC's statistics now list it as 'available'; reissue not confirmed

The RIPE NCC's statistics show it reserved on 2015-03-24 and available on 2015-03-25. The RIPE NCC keeps reserved IPv6 space next to its allocations for their growth, and the tracker didn't see this range removed from registration, so this is most likely the RIPE NCC returning such space to its pool, not a hold ending.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing the RIPE NCC's daily statistics: 2a04:fe00::/24 reserved on 2015-03-24, available on 2015-03-25 source · retrieved
  2. Before RIPE NCC delegated statistics 2015-03-24 (produced 2015-03-24T22:59:59+00:00), before the change: reserved source · retrieved
  3. After RIPE NCC delegated statistics 2015-03-25 (produced 2015-03-25T22:59:59+00:00), after the change: available source · retrieved
Classification history for this change (4 versions)
  1. : Change to the RIPE NCC's own pool record, strong inference (classifier 1.3.0)
  2. : Change to the RIPE NCC's own pool record, strong inference (classifier 1.3.1)
  3. : Change to the RIPE NCC's own pool record, strong inference (classifier 1.3.2)
  4. : Change to the RIPE NCC's own pool record, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-05-04RIPE NCC2a04:fec0::/27ReleasedHold released
2025-11-05RIPE NCC2a04:fec0::/32− DeregisteredRemoved
2022-12-19RIPE NCC2a04:fec0::/32Transfer logMerger/acquisition
2020-10-06RIPE NCC2a04:fec0::/32Transfer logIntra-RIPE NCC transfer
2020-05-07RIPE NCC2a04:fe00::/29+ RegisteredApparent reissuance
2020-05-02RIPE NCC2a04:fe00::/26ReleasedHold released
2019-11-04RIPE NCC2a04:fe00::/29− DeregisteredRemoved
2018-09-17RIPE NCC2a04:fe80::/29Transfer logIntra-RIPE NCC transfer
2018-06-13RIPE NCC2a04:fe00::/29+ RegisteredApparent reissuance
2016-12-24RIPE NCC2a04:fe00::/26ReleasedHold released
2016-06-27RIPE NCC2a04:fe00::/29− DeregisteredRemoved
2015-05-07RIPE NCC2a04:fee0::/30+ RegisteredApparent new issuance
2015-04-10RIPE NCC2a04:fec8::/29ReleasedRIPE NCC pool record
2015-04-10RIPE NCC2a04:fed0::/28ReleasedRIPE NCC pool record
2015-04-10RIPE NCC2a04:fee0::/27ReleasedRIPE NCC pool record
2015-04-09RIPE NCC2a04:fe00::/29+ RegisteredApparent new issuance
2015-04-09RIPE NCC2a04:fe40::/29+ RegisteredApparent new issuance
2015-04-09RIPE NCC2a04:fe80::/29+ RegisteredApparent new issuance
2015-04-09RIPE NCC2a04:fec0::/29+ RegisteredApparent new issuance

Transfer records (3)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCMerger acquisition2a04:fec0::/32 Avatel Sur SL RIPE NCCAVATEL TELECOM, SA RIPE NCC
RIPE NCCResource transfer2a04:fec0::/32 ESYCOR S.A. RIPE NCCCOMUNICACIONES E INFRAESTRUCTURAS DEL SUR SL RIPE NCC
RIPE NCCResource transfer2a04:fe80::/29 Netfuse Telecom Limited RIPE NCCXoom Limited RIPE NCC

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv6 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/2a04.fe00..-2a04.feff.ffff.ffff.ffff.ffff.ffff.ffff.json