rirtracker

IPv4 range · 256 addresses

185.36.100.0/24

Now

RIPE NCC statistics
Allocated (dated 2024-01-10) (TR), in the latest file
Registry
RIPE NCC
Holder
lir-tr-tips-1-MNT
From
RDAP, looked up 2026-11-04 18:19 UTC

Latest change

Transfer log Intra-RIPE NCC transfer

Reported
2026-10-28 (RIPE NCC)
Confidence
Confirmed
Inventory
No effect on RIPE NCC applicant inventory

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.

2026-10-28 RIPE NCC Transfer log Intra-RIPE NCC transfer Confirmed
Transfer log
Transfer: Joint-stock companies "Sakhalinsvyaz" (RIPE NCC) to Turkish IP Services Iletisim Sanayi Ve Ticaret Limited Sirketi (RIPE NCC)
From
Joint-stock companies "Sakhalinsvyaz" RIPE NCC
To
Turkish IP Services Iletisim Sanayi Ve Ticaret Limited Sirketi RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory

The RIPE NCC's transfer log records a transfer from Joint-stock companies "Sakhalinsvyaz" (RIPE NCC) to Turkish IP Services Iletisim Sanayi Ve Ticaret Limited Sirketi (RIPE NCC) on 2026-10-28 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.

Evidence (2) · classifier 1.4.0,
  1. Transfer log Transfer log: RESOURCE_TRANSFER on 2026-10-28 19:00 UTC, Joint-stock companies "Sakhalinsvyaz" (RIPE NCC) to Turkish IP Services Iletisim Sanayi Ve Ticaret Limited Sirketi (RIPE NCC); resources moved: 185.36.100.0/24 source · retrieved
  2. Before RIPE NCC delegated statistics 2026-10-27 (produced 2026-10-27T22:59:59+00:00), before the change: allocated (dated 2024-01-10) source · retrieved
2024-01-10 RIPE NCC + Registered Apparent reissuance of previously removed resource Observed only
Statistics
185.36.100.0/24 available on 2024-01-09, allocated on 2024-01-10
Inventory
Likely issued from RIPE NCC-controlled inventory

No transfer record matches. The RIPE NCC's statistics show it available on 2024-01-09 and allocated (dated 2024-01-10) on 2024-01-10. The tracker saw this range released from hold on 2024-01-09 (185.36.100.0/22), so it appears to have been issued again from the RIPE NCC's pool. Another change to this range was reported the day before or after (2024-01-09: Released 185.36.100.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: 185.36.100.0/24 available on 2024-01-09, allocated on 2024-01-10 source · retrieved
  2. Before RIPE NCC delegated statistics 2024-01-09 (produced 2024-01-09T22:59:59+00:00), before the change: available source · retrieved
  3. After RIPE NCC delegated statistics 2024-01-10 (produced 2024-01-10T22:59:59+00:00), after the change: allocated (dated 2024-01-10) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
  4. : Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2024-01-09RIPE NCC185.36.100.0/22ReleasedHold released
2023-07-13RIPE NCC185.36.100.0/22− DeregisteredRemoved
2013-09-27RIPE NCC185.36.100.0/22+ RegisteredApparent reissuance
2012-07-11RIPE NCC185.0.0.0/10− DeregisteredRemoved
2011-03-01RIPE NCC185.0.0.0/10+ RegisteredUnresolved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
RIPE NCCResource transfer185.36.100.0/24 Joint-stock companies "Sakhalinsvyaz" RIPE NCCTurkish IP Services Iletisim Sanayi Ve Ticaret Limited Sirketi 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

Looked upWhyRegistryHandleOrganizationStatusLast changed
After 7 days RIPE NCC185.36.100.0 - 185.36.100.255lir-tr-tips-1-MNTactive2026-10-28
After 24 hours RIPE NCC185.36.100.0 - 185.36.100.255lir-tr-tips-1-MNTactive2026-10-28
First seen RIPE NCC185.36.100.0 - 185.36.100.255lir-tr-tips-1-MNTactive2026-10-28

Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.

This page as data: ip/185.36.100.0-185.36.100.255.json