Сообщество Yandex Cloud для тех, кто хочет проверять идеи и оттачивать решения. Публикуем обновления сервисов, кейсы и новости рынка.
Наш чат: https://t.me/yandexcloud_chat
Номер заявления РКН 5609932640
Created
19 March 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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
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)
Subscribers
Change
14 Nov 2026, 13:45
23,911
-32
11 Nov 2026, 17:18
23,943
-8
10 Nov 2026, 00:21
23,951
-9
8 Nov 2026, 12:58
23,960
-7
7 Nov 2026, 07:27
23,967
-3
6 Nov 2026, 06:27
23,970
-12
5 Nov 2026, 04:21
23,982
+3
4 Nov 2026, 02:00
23,979
+3
3 Nov 2026, 04:19
23,976
-5
2 Nov 2026, 03:47
23,981
-17
1 Nov 2026, 00:46
23,998
-2
30 Oct 2026, 22:06
24,000
-2
30 Oct 2026, 01:31
24,002
-1
29 Oct 2026, 02:39
24,003
-11
28 Oct 2026, 00:56
24,014
-10
27 Oct 2026, 03:29
24,024
+18
26 Oct 2026, 02:45
24,006
-5
25 Oct 2026, 01:57
24,011
-12
23 Oct 2026, 23:20
24,023
+37
22 Oct 2026, 21:10
23,986
first 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
Window
Rolling 30 days · latest post in window 13 November 2026
Posts held
67 (28 July 2026 – 13 November 2026)
Views total
29,530
Reactions total
550
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 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
Reaction
Count
Share
Share, drawn
❤
1,134
29.6%
custom 5352821623655279348
602
15.7%
🔥
379
9.89%
custom 5341691928872264233
290
7.57%
custom 5341495412643632042
227
5.92%
🙏
190
4.96%
👍
159
4.15%
custom 5341660682985183405
123
3.21%
custom 5341537911345028143
105
2.74%
custom 5312086431538127997
89
2.32%
custom 5341684636017797278
86
2.24%
custom 5352932124573866237
71
1.85%
❤🔥
55
1.44%
custom 5341665785406330674
53
1.38%
⚡
52
1.36%
🫡
48
1.25%
👏
32
0.835%
👀
30
0.783%
🤔
18
0.47%
🌚
17
0.444%
10 further kinds
72
1.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).
Выпустили новое поколение моделей для создания голосовых ИИ-агентов 📢
Новые модели помогают агентам вести более естественный диалог и выполнять несколько связанных задач за один разговор. Технологию можно использовать для консультаций клиентов и озвучивания контента. Это позволит в десятки раз увеличить долю обращений, которые решаются без участия оператора.
🟦Модель Speech TTS Live анализирует смысл текста и адапти…
Сохранность данных, надёжность инфраструктуры и доступные мощности остаются нашими приоритетами. Рассказываем о главном в работе Yandex Cloud и даём рекомендации по переносу ресурсов между зонами доступности.
➡️ Восстановление данных
Мы восстановили доступ к 97,16% данных клиентов. Оставшиеся 2,84% восстановить невозможно из-за критических повреждений оборудования и отсутствия у клиентов бэкапов на платформе.
У кл…
Теперь вы можете использовать DeepSeek V4.1 Flash 1017 в Yandex AI Studio для своих задач 🔵
Новая версия мультимодальной рассуждающей модели для ИИ-агентов и кодовых сценариев с сегодняшнего дня доступна по API и в интерфейсе платформы.
Ещё DeepSeek V4.1 Flash 1017 можно использовать по подписке в Алисе AI Про для бизнеса и в различных интерфейсах разработки.
В версии 1017 улучшилось качество рассуждений, работы с…
Мы продолжаем делать всё, чтобы предоставить вам максимальную доступность инфраструктуры. Делимся подробностями о текущем статусе работе платформы и необходимыми инструкциями.
Новая зона доступности
Сегодня, 23 октября, открываем новую зону доступности для наших клиентов. В ней можно будет запустить вычислительные ресурсы, которые раньше размещались в зоне ru-central1-a.
Важно: доступ к новой зоне будет открыватьс…
Предупреждение: у мошенников появилась новая схема — отправлять письма от Yandex Cloud. Они просят открыть вложение из-за срочной миграции или сообщают, что аккаунт заблокирован. Как отличить письмо из Yandex Cloud от сообщения злоумышленников и что делать, если уже ответили мошенникам, — читайте в карточках.
И ещё два совета. Проверяйте статус работы сервисов Yandex Cloud только на статус-борде и в консоли, а если …
Обновили рекомендации по восстановлению работы с платформой
Сегодня актуализировали советы по отдельным сервисам, ресурсам и резервным копиями.
Если вы уже заходили на страницу вчера, пожалуйста, проверьте обновлённую версию. Будем продолжать дополнять её ежедневно.
🔗 Актуальные рекомендации на 13 октября
Мы делаем все возможное, чтобы как можно скорее восстановить работу сервисов. Остаёмся на связи ❤️
Все сервисы Yandex Cloud будут бесплатными до конца октября
Наша платформа по-прежнему работает в ограниченном режиме, а инженеры продолжают восстановительные работы.
Мы понимаем, что сейчас ваши команды сосредоточены на восстановлении своих сервисов. Чтобы в этот период вам не приходилось дополнительно беспокоиться о расходах на облако, мы приняли решение сделать использование всех сервисов Yandex Cloud во всех зо…
Собрали ответы и рекомендации по восстановлению работы с сервисами Yandex Cloud*
Понимаем, что сейчас особенно важно быстро разобраться, что происходит с вашими ресурсами и какие действия можно предпринять самостоятельно.
Наша техническая поддержка обрабатывает большой поток обращений, поэтому ответ может занять больше времени, чем обычно. Ответы на самые частые вопросы собрали в карточках.
➡️ Подробные рекомендац…
Инфраструктура наших дата-центров повреждена, поэтому в работе сервисов Яндекса могут быть сбои. Специалисты делают всё возможное, чтобы как можно скорее всё починить.
Повреждения также затронули работу службы поддержки. Если не удаётся связаться с нами через приложения, пожалуйста, пишите в официальные аккаунты сервисов Яндекса в соцсетях. Сейчас обращений много, поэтому ответ может занять больше времени, чем обычн…
В ночь с 7 на 8 октября дата-центр Яндекса в Сасово был серьезно повреждён из-за атаки БПЛА. Его работа полностью остановлена. Сегодня утром произошла атака на ещё один наш дата-центр, в Калуге. Часть инфраструктуры вышла из строя. Ни в Сасово, ни в Калуге сотрудники не пострадали. Сейчас на месте работают экстренные службы и наши специалисты.
Дата-центры — «железное сердце» Яндекса. Их работоспособность критична дл…
Открыт приём заявок на Startup2B 2026
Это ежегодный конкурс Яндекса для команд, которые развивают B2B-продукты.
✉️ Подать заявку могут команды с готовым продуктом — от ИИ-приложений до сервисов для повышения эффективности маркетинга, продаж и операционных процессов.
Эксперты выберут 15 финалистов, которые встретятся с командами Яндекса и других крупных компаний. Финал пройдёт 30 ноября в Москве. Это возможность уз…
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.
Вопрос 3. Лимиты CPU
Для контейнера задан лимит resources.limits.cpu: 500m. Под нагрузкой приложение стабильно достигает этого значения. Что произойдёт?
CPU контейнера будет троттлиться: приложение продолжит работать, но может замедлиться74%
Под будет перезапущен в соответствии с restartPolicy15%
Kubernetes автоматически увеличит лимит CPU10%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Вопрос 2. Доступность приложения
Какой объект Kubernetes помогает сохранить доступность приложения во время планового расселения подов с узлов, например при drain?
PriorityClass11%
PodDisruptionBudget56%
ResourceQuota14%
TopologySpreadConstraints19%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Вопрос 1. Cluster Autoscaler
CPU на всех узлах кластера держится около 95%, но новые поды по-прежнему успешно размещаются. Обязан ли Cluster Autoscaler добавить новый узел?
Да, если загрузка CPU превышает 80%21%
Нет, высокой загрузки CPU самой по себе недостаточно36%
Да, если в кластере включён 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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,469 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.