Data as of Nov 22, 2026

195.155.131.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
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
195.155.128.0/19
since Nov 2013
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
195.155.128.0/198,192TR-TELETEKBULUT-970731Teletek Bulut Bilisim ve Iletisim Hizmetleri A.S. (ORG-TBBV1-RIPE) · TRALLOCATED PANov 18, 2013abuse@teletek.net.tr
└ 195.155.131.0/298TELETEK-I-733337-986285unknownASSIGNED PAAug 31, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.8/298TELETEK-CUSTOMER-VD83371365unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.16/298TELETEK-N-402734-963925unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.24/298TELETEK-CUSTOMER-VD94762773unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.32/298TELETEK-CUSTOMER-VD38231021unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.40/298TELETEK-CUSTOMER-VD00971021unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.48/2816TELETEK-CUSTOMER-VD36600582unknownASSIGNED PAMay 21, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.64/298TELETEK-CUSTOMER-VD59191434unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.72/298TELETEK-CUSTOMER-VD21080533unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.80/298TELETEK-CUSTOMER-VD31021425unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.88/298TELETEK-CUSTOMER-VD51960504unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.96/2816TELETEK-CUSTOMER-VD19320504unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.112/298TELETEK-CUSTOMER-VD82171471unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.160/298TELETEK-CUSTOMER-VD49481232unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.168/298TELETEK-CUSTOMER-VD29331364unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.176/298TELETEK-CUSTOMER-VD95121232unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.184/298TELETEK-CUSTOMER-VD56200550unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.192/298TELETEK-CUSTOMER-VD78011321unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.208/304TELETEK-CUSTOMER-VD65341060unknownASSIGNED PASep 11, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.212/304TELETEK-CUSTOMER-VD82260533unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.216/298TELETEK-CUSTOMER-VD73901233unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.224/2816TELETEK-CUSTOMER-VD68350315unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.240/304TELETEK-CUSTOMER-VD78042866unknownASSIGNED PASep 21, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.244/304TELETEK-CUSTOMER-VD72161247unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.248/304TELETEK-CUSTOMER-VD13190897unknownASSIGNED PAApr 30, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731
└ 195.155.131.252/304TELETEK-G-142935-660928unknownASSIGNED PAMay 16, 2026abuse@teletek.net.tr
via TR-TELETEKBULUT-970731

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jun 2021
Current origin since
Jul 2025 · 1.4 yr
Origin networks
1