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

37.9.200.0/24

No anonymizer space · no proxy exits in 30 days

Teletek Bulut Bilisim ve Iletisim Hizmetleri A.S.

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
37.9.200.0/21
since Feb 2012
AS43352HostingTeletek Bulut Bilisim ve Iletisim Hizmetleri A.S.

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
37.9.200.0/212,048TR-TELETEKBULUT-20111215Teletek Bulut Bilisim ve Iletisim Hizmetleri A.S. (ORG-TBBV1-RIPE) · TRALLOCATED PADec 15, 2011abuse@teletek.net.tr
└ 37.9.200.16/298TELETEK-Z-082450-111099unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.24/298TELETEK-V-532404-555742unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.32/298TELETEK-CUSTOMER-VD74582840unknownASSIGNED PAJul 13, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.40/298TELETEK-Y-278904-783362unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.48/2816TELETEK-CUSTOMER-VD15162798unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.128/298TELETEK-CUSTOMER-VD09750449unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.136/304TELETEK-CUSTOMER-VD87180971unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.140/304TELETEK-CUSTOMER-VD48420806unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.144/298TELETEK-CUSTOMER-VD14340977unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.152/298TELETEK-CUSTOMER-VD40071277unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.160/298TELETEK-CUSTOMER-VD00981207unknownASSIGNED PAMay 1, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.168/298TELETEK-CUSTOMER-VD46700005unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.176/298TELETEK-M-880061-947731unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.184/298TELETEK-CUSTOMER-VD59290858unknownASSIGNED PAMay 7, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.192/298TELETEK-CUSTOMER-VD40281207unknownASSIGNED PAMay 1, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.200/298TELETEK-M-922690-307137unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.208/2816TELETEK-R-327469-957785unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215
└ 37.9.200.224/2732TELETEK-Y-726487-506436unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-20111215

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2012
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1