Data as of Nov 13, 2026

31.210.89.0/24

No anonymizer space · no proxy exits in 30 days

Radore Veri Merkezi Hizmetleri A.S.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.210.64.0/1816,384TR-RADORE-20110504Radore Veri Merkezi Hizmetleri A.S. (ORG-RHTH1-RIPE) · TRALLOCATED PAMay 4, 2011abuse@radore.com
└ 31.210.89.64/2732ozgurekinci-com-50300ozgurekinci.com - IPv4 NetworkASSIGNED PAMay 29, 2019abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.96/2732TCM-36134TCM - IPv4 NetworkASSIGNED PAMar 13, 2017abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.160/2816kitapstore2_yeni-53236kitapstore2 yeni - IPv4 NetworkASSIGNED PAMay 2, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.176/298cerinfo-54706cerinfo - IPv4 NetworkASSIGNED PAMay 3, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.192/298R210-36566R210 - IPv4 NetworkASSIGNED PAFeb 8, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.200/298lena-yeni-56201lena-yeni - IPv4 NetworkASSIGNED PAFeb 23, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.208/298SolidElectron-55096SolidElectron - IPv4 NetworkASSIGNED PAMar 1, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.216/298kosmoslabs-37112kosmoslabs - IPv4 NetworkASSIGNED PAMar 2, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.224/298VOIP-30077VOIP - IPv4 NetworkASSIGNED PAMar 7, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.232/298ssr2367-org-54441ssr2367.org - IPv4 NetworkASSIGNED PAMar 7, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.240/298DatasisDNS-55815DatasisDNS - IPv4 NetworkASSIGNED PAMar 14, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.89.248/298TR-Turistik-50377TR-Turistik - IPv4 NetworkASSIGNED PAMar 21, 2016abuse@radore.com
via TR-RADORE-20110504

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2011
Current origin since
May 2026 · 6 mo
Origin networks
1