Transferred into APNIC administration; not a new issuance
Timeline (3)
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.
2021-04-01APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: TMNSI (ARIN) to Sattelite Plus Incorporated (APNIC)
From
TMNSI ARIN
To
Sattelite Plus Incorporated APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2021-03-31. Lists that cover every registry show it there.
Inventory
Transferred into APNIC administration; not a new issuance
APNIC's transfer log records a transfer from TMNSI (ARIN) to Sattelite Plus Incorporated (APNIC) on 2021-03-31 20:42 UTC: it came to APNIC from ARIN. It was already issued by another registry, so this is not a new issuance.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2021-03-31 20:42 UTC, TMNSI (ARIN) to Sattelite Plus Incorporated (APNIC); resources moved: 104.255.36.0/22source · retrieved
BeforeAPNIC delegated statistics 2021-04-01, before the change: not listedsource · retrieved
AfterAPNIC delegated statistics 2021-04-02, after the change: allocated (dated 2018-08-17)source · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.0)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.1)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.2)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.4.0) current
2021-03-31ARINNot in ARIN-IssuedInter-RIR transfer out of ARINConfirmed
Transferred out of ARIN administration; not offered to ARIN applicants
ARIN's transfer log records a transfer from TMNS, Inc. (ARIN) to Sattelite Plus Inc (APNIC) on 2021-03-31 20:52 UTC: it left ARIN for APNIC. ARIN-Issued didn't list this change; it is not a new allocation and is not offered to ARIN applicants.
Evidence (4) · classifier 1.4.0,
StatisticsNot listed in ARIN-Issued; found by comparing ARIN's daily statistics: 104.255.36.0/22 allocated on 2021-03-31, not listed on 2021-04-01source · retrieved
Transfer logTransfer log: RESOURCE_TRANSFER on 2021-03-31 20:52 UTC, TMNS, Inc. (ARIN) to Sattelite Plus Inc (APNIC); resources moved: 104.255.36.0/22source · retrieved
BeforeARIN delegated statistics 2021-03-30 (produced 2021-03-30T14:00:13+00:00), before the report: allocated (dated 2018-08-17)source · retrieved
AfterARIN delegated statistics 2021-04-01 (produced 2021-04-01T14:00:13+00:00), after the report: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.4.0) current
2018-08-17ARIN+ AddApparent reissuance of previously removed resourceStrong inference
ARIN-Issued
Add 104.255.36.0-104.255.39.255
Inventory
Likely issued from ARIN-controlled inventory
No transfer record matches. ARIN's statistics show it reserved on 2018-08-16 and allocated (dated 2018-08-17) on 2018-08-18. The tracker saw this range released from hold on 2018-06-01 (104.255.32.0-104.255.39.255), so it appears to have been issued again from ARIN's pool.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2018-08-17: "Add 104.255.36.0-104.255.39.255"source · retrieved
BeforeARIN delegated statistics 2018-08-16 (produced 2018-08-16T05:00:23+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2018-08-18 (produced 2018-08-18T05:00:23+00:00), after the report: allocated (dated 2018-08-17)source · retrieved
Classification history for this change (4 versions)
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.