Telegram RegisterThe public register of Telegram
Telegram profile photo for Yandex Cloud

Channel

Yandex Cloud

@yandexcloudnews

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

23,911subscribers

+2,983 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001162720642
TypeChannel
Username@yandexcloudnews
DescriptionСообщество Yandex Cloud для тех, кто хочет проверять идеи и оттачивать решения. Публикуем обновления сервисов, кейсы и новости рынка. Наш чат: https://t.me/yandexcloud_chat Номер заявления РКН 5609932640
Created19 March 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/yandexcloudnews

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

20,91224,02422,46823,9116 August 202614 November 2026
65 measurements spanning 100 days, net +2,983. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 20,445–24,491 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 13:4523,911-32
11 Nov 2026, 17:1823,943-8
10 Nov 2026, 00:2123,951-9
8 Nov 2026, 12:5823,960-7
7 Nov 2026, 07:2723,967-3
6 Nov 2026, 06:2723,970-12
5 Nov 2026, 04:2123,982+3
4 Nov 2026, 02:0023,979+3
3 Nov 2026, 04:1923,976-5
2 Nov 2026, 03:4723,981-17
1 Nov 2026, 00:4623,998-2
30 Oct 2026, 22:0624,000-2
30 Oct 2026, 01:3124,002-1
29 Oct 2026, 02:3924,003-11
28 Oct 2026, 00:5624,014-10
27 Oct 2026, 03:2924,024+18
26 Oct 2026, 02:4524,006-5
25 Oct 2026, 01:5724,011-12
23 Oct 2026, 23:2024,023+37
22 Oct 2026, 21:1023,986first reading

Engagement

67 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 124 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
30.9%
avg views ÷ 23,911 subscribers
Avg views / post
7,380
4 posts measured
Reaction rate
1.86%
reactions ÷ views · ER floor
Posts in window
4
of 67 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held67 (28 July 2026 – 13 November 2026)
Views total29,530
Reactions total550
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 06:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈2,580
Videos
≈94
Links
≈2,090

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
21s
Average length
21s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

3,832 reactions across 65 posts, in 30 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,13429.6%
custom 535282162365527934860215.7%
🔥3799.89%
custom 53416919288722642332907.57%
custom 53414954126436320422275.92%
🙏1904.96%
👍1594.15%
custom 53416606829851834051233.21%
custom 53415379113450281431052.74%
custom 5312086431538127997892.32%
custom 5341684636017797278862.24%
custom 5352932124573866237711.85%
❤‍🔥551.44%
custom 5341665785406330674531.38%
⚡521.36%
🫡481.25%
👏320.835%
👀300.783%
🤔180.47%
🌚170.444%
10 further kinds721.88%

Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 66 of the 67 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3,856 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 67 most recent posts we hold, published 28 July 2026 to 13 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 4 posts held from the last 30 days (25.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 10:24 UTC≈2,640 views44 reactionsread 17 November 2026
Photo

Выпустили новое поколение моделей для создания голосовых ИИ-агентов 📢 Новые модели помогают агентам вести более естественный диалог и выполнять несколько связанных задач за один разговор. Технологию можно использовать для консультаций клиентов и озвучивания контента. Это позволит в десятки раз увеличить долю обращений, которые решаются без участия оператора. 🟦Модель Speech TTS Live анализирует смысл текста и адапти…

❤20custom 534169192887226423310custom 53416657854063306748custom 53416606829851834054👍2

10 Nov 2026, 12:05 UTC≈6,770 views116 reactionsread 17 November 2026
Photo

Сохранность данных, надёжность инфраструктуры и доступные мощности остаются нашими приоритетами. Рассказываем о главном в работе Yandex Cloud и даём рекомендации по переносу ресурсов между зонами доступности. ➡️ Восстановление данных Мы восстановили доступ к 97,16% данных клиентов. Оставшиеся 2,84% восстановить невозможно из-за критических повреждений оборудования и отсутствия у клиентов бэкапов на платформе. У кл…

❤59👏15custom 534149541264363204214custom 535282162365527934814🫡4🌚2🏆2😱2

2 Nov 2026, 11:04 UTC≈6,420 views45 reactionsread 17 November 2026
Photo

Теперь вы можете использовать DeepSeek V4.1 Flash 1017 в Yandex AI Studio для своих задач 🔵 Новая версия мультимодальной рассуждающей модели для ИИ-агентов и кодовых сценариев с сегодняшнего дня доступна по API и в интерфейсе платформы. Ещё DeepSeek V4.1 Flash 1017 можно использовать по подписке в Алисе AI Про для бизнеса и в различных интерфейсах разработки. В версии 1017 улучшилось качество рассуждений, работы с…

❤26👍11custom 53416919288722642338

23 Oct 2026, 14:48 UTC≈13,700 views345 reactionsread 17 November 2026
Photo

Мы продолжаем делать всё, чтобы предоставить вам максимальную доступность инфраструктуры. Делимся подробностями о текущем статусе работе платформы и необходимыми инструкциями. Новая зона доступности Сегодня, 23 октября, открываем новую зону доступности для наших клиентов. В ней можно будет запустить вычислительные ресурсы, которые раньше размещались в зоне ru-central1-a. Важно: доступ к новой зоне будет открыватьс…

custom 5352821623655279348150🔥90custom 534169192887226423349❤20custom 534153791134502814316👍11🎉8🫡1

14 Oct 2026, 08:03 UTC≈10,300 views99 reactionsread 17 November 2026
Forwarded from @yandexPhoto

Предупреждение: у мошенников появилась новая схема — отправлять письма от Yandex Cloud. Они просят открыть вложение из-за срочной миграции или сообщают, что аккаунт заблокирован. Как отличить письмо из Yandex Cloud от сообщения злоумышленников и что делать, если уже ответили мошенникам, — читайте в карточках. И ещё два совета. Проверяйте статус работы сервисов Yandex Cloud только на статус-борде и в консоли, а если …

❤40🙏33custom 534169192887226423321🤩5

13 Oct 2026, 15:30 UTC≈11,300 views116 reactionsread 17 November 2026

Обновили рекомендации по восстановлению работы с платформой Сегодня актуализировали советы по отдельным сервисам, ресурсам и резервным копиями. Если вы уже заходили на страницу вчера, пожалуйста, проверьте обновлённую версию. Будем продолжать дополнять её ежедневно. 🔗 Актуальные рекомендации на 13 октября Мы делаем все возможное, чтобы как можно скорее восстановить работу сервисов. Остаёмся на связи ❤️

custom 535282162365527934856🙏24custom 534169192887226423311custom 53529321245738662378❤7🌚4👍3🔥3

13 Oct 2026, 09:00 UTC≈28,500 views400 reactionsread 17 November 2026

Все сервисы Yandex Cloud будут бесплатными до конца октября Наша платформа по-прежнему работает в ограниченном режиме, а инженеры продолжают восстановительные работы. Мы понимаем, что сейчас ваши команды сосредоточены на восстановлении своих сервисов. Чтобы в этот период вам не приходилось дополнительно беспокоиться о расходах на облако, мы приняли решение сделать использование всех сервисов Yandex Cloud во всех зо…

🔥139custom 5352821623655279348121❤55custom 534169192887226423332custom 535293212457386623725🙏21custom 53416846360177972784🫡3

12 Oct 2026, 16:21 UTC≈13,300 views164 reactionsread 17 November 2026
Photo

Собрали ответы и рекомендации по восстановлению работы с сервисами Yandex Cloud* Понимаем, что сейчас особенно важно быстро разобраться, что происходит с вашими ресурсами и какие действия можно предпринять самостоятельно. Наша техническая поддержка обрабатывает большой поток обращений, поэтому ответ может занять больше времени, чем обычно. Ответы на самые частые вопросы собрали в карточках. ➡️ Подробные рекомендац…

custom 535282162365527934883❤50custom 534169192887226423325🫡3🤔2🔥1

11 Oct 2026, 08:48 UTC≈7,280 views400 reactionsread 17 November 2026
Forwarded from @yandexPhoto

Инфраструктура наших дата-центров повреждена, поэтому в работе сервисов Яндекса могут быть сбои. Специалисты делают всё возможное, чтобы как можно скорее всё починить. Повреждения также затронули работу службы поддержки. Если не удаётся связаться с нами через приложения, пожалуйста, пишите в официальные аккаунты сервисов Яндекса в соцсетях. Сейчас обращений много, поэтому ответ может занять больше времени, чем обычн…

❤195custom 5352821623655279348150custom 535293212457386623721❤‍🔥15🫡5🌚4🦄4🔥3

9 Oct 2026, 08:47 UTC≈8,210 views532 reactionsread 17 November 2026
Forwarded from @yandexPhoto

В ночь с 7 на 8 октября дата-центр Яндекса в Сасово был серьезно повреждён из-за атаки БПЛА. Его работа полностью остановлена. Сегодня утром произошла атака на ещё один наш дата-центр, в Калуге. Часть инфраструктуры вышла из строя. Ни в Сасово, ни в Калуге сотрудники не пострадали. Сейчас на месте работают экстренные службы и наши специалисты. Дата-центры — «железное сердце» Яндекса. Их работоспособность критична дл…

❤292🙏110❤‍🔥40custom 535282162365527934828🫡25custom 535293212457386623717👏9🔥7

7 Oct 2026, 09:15 UTC≈11,000 views39 reactionsread 17 November 2026

Posted without readable text

❤15custom 534153791134502814311custom 53416606829851834057🤔3custom 53416846360177972782custom 53439881257628828761

6 Oct 2026, 09:58 UTC≈8,010 views27 reactionsread 17 November 2026
Photo

Открыт приём заявок на Startup2B 2026 Это ежегодный конкурс Яндекса для команд, которые развивают B2B-продукты. ✉️ Подать заявку могут команды с готовым продуктом — от ИИ-приложений до сервисов для повышения эффективности маркетинга, продаж и операционных процессов. Эксперты выберут 15 финалистов, которые встретятся с командами Яндекса и других крупных компаний. Финал пройдёт 30 ноября в Москве. Это возможность уз…

❤13custom 53416919288722642335🦄4custom 53415379113450281433custom 53414954126436320422

Showing the 12 most recent of 67 posts we hold for @yandexcloudnews. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Posts edited after publishing

@yandexcloudnews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 November 2026
Most recent edit
11 November 2026

Polls

The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

2 Oct 2026, 08:43 UTCAnonymous Poll138 voters

А какой поиск чаще всего нужен вам?

  1. По точному совпадению17%
  2. По смыслу10%
  3. И по смыслу, и по точным данным62%
  4. Пока хватает обычного поиска12%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 12:02 UTCAnonymous Quiz338 voters

Вопрос 3. Лимиты CPU Для контейнера задан лимит resources.limits.cpu: 500m. Под нагрузкой приложение стабильно достигает этого значения. Что произойдёт?

  1. CPU контейнера будет троттлиться: приложение продолжит работать, но может замедлиться74%
  2. Под будет перезапущен в соответствии с restartPolicy15%
  3. Kubernetes автоматически увеличит лимит CPU10%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 12:02 UTCAnonymous Quiz268 voters

Вопрос 2. Доступность приложения Какой объект Kubernetes помогает сохранить доступность приложения во время планового расселения подов с узлов, например при drain?

  1. PriorityClass11%
  2. PodDisruptionBudget56%
  3. ResourceQuota14%
  4. TopologySpreadConstraints19%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 12:02 UTCAnonymous Quiz288 voters

Вопрос 1. Cluster Autoscaler CPU на всех узлах кластера держится около 95%, но новые поды по-прежнему успешно размещаются. Обязан ли Cluster Autoscaler добавить новый узел?

  1. Да, если загрузка CPU превышает 80%21%
  2. Нет, высокой загрузки CPU самой по себе недостаточно36%
  3. Да, если в кластере включён HPA43%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 67 most recent posts we hold, published 28 July 2026 to 13 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 24 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Yandex Cloud Alerts
@yandexcloudalerts · 19,656
#1
Inside Yandex Cloud
@cloud_track · 8,359
#2
VK Cloud
@vk_cloud_news · 3,261
#3
Yandex Scale 2026
@yandexscale · 7,160
#4
Yandex Infrastructure
@yandex_infrastructure · 4,817
#5
Яндекс
@yandex · 596,538
#6
Selectel
@Selectel · 62,346
#7
k8s (in)security
@k8security · 13,330
#8
Yandex B2B Tech Partners
@YandexB2BTechPartners · 1,459
#9
Yandex for Developers
@Yandex4Developers · 28,673
#10
ТЕХНО: Яндекс про технологии
@techno_yandex · 217,669
#11
Хабр
@habr_com · 134,799
#12
Вокруг Kubernetes в VK
@k8s_vk · 4,312
#13
Пятничный деплой
@count0_digest · 4,823
#14
K2 Cloud Live
@k2cloudlive · 1,899
#15
Cloud.ru
@cloudruprovider · 10,708
#16
DevOps FM
@devops_fm · 5,296
#17
Beeline Cloud
@datafort_live · 1,245
#18
Как мы делаем Яндекс
@yandexhabr · 3,414
#19
The After Times
@theaftertimes · 16,839
#20
Мониторим ИТ
@monitorim_it · 8,578
#21
The Art Of Programming
@taoplive · 2,484
#22
AWS Notes
@aws_notes · 5,864
#23
Selectel [команда]
@selectelcareers · 11,720
#24
YDEX
@ydex_forinvestors · 15,431
#25
Hilbert Team | Эксперты в DevOps
@hilbertteam · 753
#26
DevOps Deflope News
@devops_deflope · 5,829
#27
Timeweb.Cloud News
@timewebru · 17,969
#28
Yandex for Backend
@yandexforbackend · 10,258
#29
Yandex for Products
@yandexforproducts · 18,007
#30
Цифровизируй это
@digitize_IT · 1,525
#31
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs · 33,174
#32
Слёрм
@slurmnews · 7,959
#33
Ozon Tech
@ozon_tech · 30,231
#34
KazDevOps
@DevOpsKaz · 6,970
#35
Young&&Yandex
@Young_and_Yandex · 113,000
#36
DevSecOps Talks
@devsecops_weekly · 8,089
#37
AvitoTech
@avitotech · 25,824
#38
К2Тех
@k2_tech · 1,812
#39
Инжиниринг Данных
@rockyourdata · 23,687
#40
TAdviser
@tadviser · 13,471
#41
GigaChat
@official_gigachat · 302,578
#42
Данные на стероидах
@sterodata · 3,258
#43
МWS Cloud
@MWS_Cloud · 11,296
#44
Минцифры России
@mintsifry · 232,126
#45
Новости Москвы
@moscowmap · 2,617,403
#46
КОНТЕКСТ
@kontext_channel · 864,338
#47
Яндекс 360
@yandex360blog · 45,195
#48
RCCPA (CloudPro)
@rccpa · 1,194
#49
Rozetked
@rozetked · 644,947
#50
vc.ru
@vcnews · 112,196
#51
42 секунды
@ftsec · 19,374
#52
Артемий Лебедев
@temalebedev · 965,472
#53
linkmeup
@linkmeup_podcast · 17,587
#54
Код.ру
@d_code · 405,435
#55
DevOps&SRE Library
@devopslibrary · 19,860
#56
Эксплойт
@exploitex · 2,020,421
#57
Яндекс Музей
@yandexmuseum · 9,063
#58
Антонов такой Антонов
@auantonov · 321,252
#59
ИТ-Пикник
@IT_picnic · 22,737
#60
Флант | Специалисты по DevOps и Kubernetes
@flant_ru · 2,171
#61
РТК-ЦОД
@rtc_dc · 3,279
#62
Технологический Болт Генона
@tech_b0lt_Genona · 10,642
#63
эйай ньюз
@ai_newz · 98,429
#64
Бэкдор
@whackdoor · 1,531,148
#65
commit -m "better"
@itpgchannel · 4,120
#66
Телекоммуналка
@telecommunal · 43,845
#67
Утечки информации
@dataleak · 117,550
#68
КРОК
@croc_it · 7,205
#69
Т-Инвестиции
@tb_invest_official · 520,552
#70
TechSparks
@techsparks · 46,732
#71
Книжный куб
@book_cube · 19,399
#72
Denis Sexy IT 🤖
@denissexy · 140,992
#73
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,561
#74
Кубернетичек
@k8sjust · 1,078
#75
Пост Лукацкого
@alukatsky · 38,486
#76
ЗаТелеком 🌐
@zatelecom · 64,456
#77
Группа Астра
@astragroup · 9,481
#78
Сбер
@sberbank · 725,662
#79
Сиолошная
@seeallochnaya · 81,455
#80
Уставший техдир
@tired_glebmikheev · 18,735
#81
CNews.ru
@CNewsDaily · 15,781
#82
Яндекс Пэй
@yandexfintech · 202,171
#83
Нецифровая экономика
@antidigital · 24,475
#84
eucariot
@ieucariot · 1,432
#85
ServerAdmin.ru
@srv_admin · 32,699
#86
Заметки на техдирском
@ctorecords · 10,855
#87
Раньше всех. Ну почти.
@bbbreaking · 1,974,594
#88
Mash
@mash · 3,136,893
#89
Банкста
@banksta · 439,853
#90
addmeto
@addmeto · 72,033
#91
РБК. Новости. Главное
@rbc_news · 912,321
#92
Дудь
@yurydud · 848,551
#93
Tynu40k Goblina (oper.ru)
@oper_goblin · 489,965
#94
Т-Банк
@tbank · 330,178
#95
ServerNews
@servernewsru · 2,598
#96
Gravity UI News
@gravity_ui · 891
#97

Read from Telegram’s recommendation API, most recently 22 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Selectel
@Selectel · 62,346
Telegram ranks this channel #2 of 96 here — alongside 95 others — read 21 August 2026
Яндекс 360
@yandex360blog · 45,195
Telegram ranks this channel #8 of 97 here — alongside 96 others — read 27 August 2026
Яндекс
@yandex · 596,538
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 9 August 2026
Yandex for Developers
@Yandex4Developers · 28,673
Telegram ranks this channel #19 of 94 here — alongside 93 others — read 9 September 2026
Timeweb Cloud Alerts
@timewebcloud_alerts · 25,846
Telegram ranks this channel #23 of 87 here — alongside 86 others — read 9 September 2026
IT STAND
@ITSTAND_ORG · 164,398
Telegram ranks this channel #23 of 98 here — alongside 97 others — read 9 September 2026
Яндекс Практикум
@yndx_practicum · 33,808
Telegram ranks this channel #26 of 97 here — alongside 96 others — read 3 September 2026
ТЕХНО: Яндекс про технологии
@techno_yandex · 217,669
Telegram ranks this channel #30 of 96 here — alongside 95 others — read 11 August 2026
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs · 33,174
Telegram ranks this channel #39 of 96 here — alongside 95 others — read 5 September 2026
DevOps by REBRAIN
@rebrain_devops · 28,705
Telegram ranks this channel #40 of 94 here — alongside 93 others — read 9 September 2026
АвтоДен
@AutoDen1 · 35,857
Telegram ranks this channel #41 of 55 here — alongside 54 others — read 2 September 2026
Devops Jobs — вакансии и резюме
@devops_jobs_feed · 22,323
Telegram ranks this channel #43 of 95 here — alongside 94 others — read 22 September 2026
Игромир
@Igromir_cloud · 57,161
Telegram ranks this channel #45 of 89 here — alongside 88 others — read 22 August 2026
Яндекс Пэй
@yandexfintech · 202,171
Telegram ranks this channel #49 of 88 here — alongside 87 others — read 12 August 2026
DevOps community for love
@devopsforlove · 44,606
Telegram ranks this channel #54 of 95 here — alongside 94 others — read 9 September 2026
Kaspersky
@kasperskylab_ru · 29,326
Telegram ranks this channel #55 of 96 here — alongside 95 others — read 9 September 2026
АТОМ
@atom_auto · 23,452
Telegram ranks this channel #56 of 94 here — alongside 93 others — read 15 September 2026
DevOps&SRE Library
@devopslibrary · 19,860
Telegram ranks this channel #59 of 94 here — alongside 93 others — read 30 September 2026
Барнаул * Новости * Важное
@Barnaul_vajnoe · 25,336
Telegram ranks this channel #68 of 75 here — alongside 74 others — read 23 September 2026
билайн
@beeline · 21,653
Telegram ranks this channel #68 of 95 here — alongside 94 others — read 23 September 2026
Код Желтый
@kod_zheltyi · 33,570
Telegram ranks this channel #94 of 96 here — alongside 95 others — read 4 September 2026

This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Yandex Cloud” (@yandexcloudnews), 23,911 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/yandexcloudnews.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.