LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

31.210.64.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
AS42926
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.64.16/298R410-36565R410 - IPv4 NetworkASSIGNED PASep 4, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.24/304fotopazar-24648fotopazar - IPv4 NetworkASSIGNED PASep 4, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.28/304Odeal-Mysql-56760Odeal-Mysql - IPv4 NetworkASSIGNED PASep 4, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.64/298ATVMPR1-23402ATVMPR1 - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.72/298Bigpoint-38201Bigpoint - IPv4 NetworkASSIGNED PASep 5, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.80/298MODAGO-54679MODAGO - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.88/298RadoreRadore Veri MerkeziASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.96/304softtr11-51717softtr11 - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.100/304Netisler-27425Netisler - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.104/298ZANHAGROUP-55500ZANHAGROUP - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.112/298umutbas-43664umutbas - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.128/298linonno-23601linonno - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.136/298clockwork-15996clockwork - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.144/298ayazsoft-31382ayazsoft - IPv4 NetworkASSIGNED PAJun 3, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.152/304omegadedicated-51185omegadedicated - IPv4 NetworkASSIGNED PAMay 10, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.156/304StarkPhysical6-31043StarkPhysical6 - IPv4 NetworkASSIGNED PAMay 10, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.160/298birtekhost-16072birtekhost - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.168/298ssr2615-edu-55404ssr2615.edu - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.176/298egitek-36282egitek - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.184/298cankat1-15022cankat1 - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.192/298hw01-16104hw01 - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.200/304Eta-56102Eta - IPv4 NetworkASSIGNED PANov 4, 2021abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.204/304seyidoglu-43227seyidoglu - IPv4 NetworkASSIGNED PAJan 2, 2016abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.208/298RadoreRadore Veri MerkeziASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.216/304medulaserver-20566medulaserver - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.220/304VENDORARENA-52232VENDORARENA - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.224/298juenpet3-55672juenpet3 - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.232/298yazilimcin-com-23980yazilimcin.com - IPv4 NetworkASSIGNED PASep 13, 2015abuse@radore.com
via TR-RADORE-20110504
└ 31.210.64.240/2816AYHAN-46041AYHAN - IPv4 NetworkASSIGNED PAJul 10, 2012abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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