Telegram RegisterThe public register of Telegram
Telegram profile photo for DevOps by REBRAIN

Channel

DevOps by REBRAIN

@rebrain_devops

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

28,873subscribers

-112 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-1001155329936
TypeChannel
Username@rebrain_devops
DescriptionОткрытые практикумы по DevOps, Linux, Golang, Networks, Security Мы на связи: [email protected] +7 (499) 116-34-68 https://rebrainme.com/ Зарегистрированы в РКН: https://knd.gov.ru/license?id=674db558d793bc0b0b8845ff&registryType=bloggersPermission
Created6 February 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/rebrain_devops

Topic

Education — 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 73% 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 why it has no browse page of its own yet.

Growth

28,82228,98528,903.56 August 2026 — 28,985 subscribers7 August 2026 — 28,984 subscribers8 August 2026 — 28,975 subscribers9 August 2026 — 28,974 subscribers11 August 2026 — 28,969 subscribers12 August 2026 — 28,968 subscribers14 August 2026 — 28,961 subscribers15 August 2026 — 28,955 subscribers16 August 2026 — 28,954 subscribers17 August 2026 — 28,955 subscribers18 August 2026 — 28,944 subscribers19 August 2026 — 28,939 subscribers20 August 2026 — 28,930 subscribers21 August 2026 — 28,924 subscribers23 August 2026 — 28,925 subscribers24 August 2026 — 28,918 subscribers25 August 2026 — 28,905 subscribers26 August 2026 — 28,900 subscribers27 August 2026 — 28,897 subscribers29 August 2026 — 28,893 subscribers30 August 2026 — 28,892 subscribers1 September 2026 — 28,884 subscribers2 September 2026 — 28,876 subscribers3 September 2026 — 28,871 subscribers5 September 2026 — 28,860 subscribers9 September 2026 — 28,845 subscribers11 September 2026 — 28,828 subscribers13 September 2026 — 28,833 subscribers15 September 2026 — 28,822 subscribers17 September 2026 — 28,865 subscribers19 September 2026 — 28,890 subscribers26 September 2026 — 28,873 subscribers28,8736 August 202626 September 2026
32 measurements spanning 51 days, net -112. 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 28,798–29,009 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
26 Sept 2026, 19:3628,873-17
19 Sept 2026, 17:1728,890+25
17 Sept 2026, 03:3928,865+43
15 Sept 2026, 03:5528,822-11
13 Sept 2026, 14:1928,833+5
11 Sept 2026, 19:3728,828-17
9 Sept 2026, 05:1728,845-15
5 Sept 2026, 18:5728,860-11
3 Sept 2026, 19:3728,871-5
2 Sept 2026, 13:0428,876-8
1 Sept 2026, 15:1228,884-8
30 Aug 2026, 11:4528,892-1
29 Aug 2026, 14:5528,893-4
27 Aug 2026, 18:2728,897-3
26 Aug 2026, 19:5428,900-5
25 Aug 2026, 19:3328,905-13
24 Aug 2026, 20:4528,918-7
23 Aug 2026, 07:1228,925+1
21 Aug 2026, 20:0528,924-6
20 Aug 2026, 20:0428,930first reading

Engagement

91 posts held, back to 22 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 88 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.5%
avg views ÷ 28,873 subscribers
Avg views / post
3,320
34 posts measured
Reaction rate
0.523%
reactions ÷ views · ER floor
Posts in window
34
of 91 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 1 October 2026
Posts held91 (22 July 2026 – 1 October 2026)
Views total112,870
Reactions total590
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Oct 2026, 11:54 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
≈525
Videos
≈14
Links
≈1,100

Lifetime counters from Telegram’s own channel header, read 2 October 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
9m 54s
Average length
9m 54s

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

1,303 reactions across 84 posts, in 7 distinct kinds. The most used accounts for 49.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥64149.2%
👍33926.0%
❤21116.2%
😁372.84%
👏332.53%
💯241.84%
👎181.38%

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 84 of the 91 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 1,303 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 91 most recent posts we hold, published 22 July 2026 to 1 October 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

1 Oct 2026, 16:20 UTC≈1,440 views5 reactionsread 2 October 2026
Photo

🔥Новый практикум AWS Cloud Fundamentals Всем, кто ранее покупал AWS, курс будет доступно бесплатно, а для новых участников можно активировать демодоступ. Программа разработана специально для системных администраторов, DevOps-инженеров и разработчиков, которым необходимо быстро и безболезненно войти в мир облачной инфраструктуры AWS. Мы убрали всю теоретическую воду и сфокусировались на жесткой практике: от безопасн…

🔥5

30 Sept 2026, 16:30 UTC≈1,600 views2 reactionsread 1 October 2026

❗ Открытый практикум Log4Shell на пальцах: как я попал на сервер через заголовок User-Agent идёт уже 30 минут Если вы ещё не с нами, скорее подключайтесь! Ссылка для входа: https://my.rebrainme.com/live-class/582 🔥 Задать вопрос по практикуму и обсудить детали можно в нашем чате

🔥2

30 Sept 2026, 15:55 UTC≈1,780 views1 reactionsread 1 October 2026

❗Начало Открытого практикума Log4Shell на пальцах: как я попал на сервер через заголовок User-Agent уже через 5 минут Встречаемся в 19:00 МСК. Ссылка для входа: https://my.rebrainme.com/live-class/582 Также вы можете подключиться к вебинару через личный кабинет, в разделе «Вебинары». 🔥 Задать вопрос по практикуму и обсудить детали можно в нашем чате

🔥1

30 Sept 2026, 15:01 UTC≈1,780 views1 reactionsread 1 October 2026

Открытый практикум Log4Shell на пальцах: как я попал на сервер через заголовок User-Agent начнётся сегодня в 19:00 МСК. Практикум будет проходить на площадке Zoom.US Важно!!! Чтобы вы смогли без проблем к нам присоединиться, заранее протестируйте комнату по ссылке: https://zoom.us/test Ссылку для доступа отправим вам за 5 минут до начала. Либо заходите через личный кабинет в разделе «Вебинары». 🔥 Задать вопрос по …

🔥1

30 Sept 2026, 14:36 UTC≈2,020 views4 reactionsread 2 October 2026

Как собрать полноценный REST/gRPC сервис на Go? Хендлер на Go, который отдаёт JSON, пишется за вечер. Проблемы начинаются, когда этот код уезжает в Kubernetes. При деплое под получает SIGTERM и обрывает запросы на середине. Клиент уже закрыл соединение, а запрос к PostgreSQL продолжает работать и грузить базу. В логах тысячи строк, и по ним не понять, какие относятся к упавшему запросу. Тесты на моках зеленые, а с …

👍4

30 Sept 2026, 07:00 UTC≈2,040 views8 reactionsread 1 October 2026

🗓️ Расписание вебинаров на сегодня ⏰ 19:00 МСК - Log4Shell на пальцах: как я попал на сервер через заголовок User-Agent 🔗 Регистрация и программа О вебинаре напомним за 5 минут до начала на этом канале. Также вы сможете зайти через личный кабинет. 🔥 Задать вопросы и обсудить детали можно в нашем чате

🔥4👍3👏1

29 Sept 2026, 13:13 UTC≈2,260 views13 reactionsread 2 October 2026
Photo

Red Team vs Blue Team. Почему защите учатся у тех, кто ломает Админ полгода настраивал домен: сложные пароли, отдельные учётки под сервисы, антивирус на каждой машине. Пентестер получил Domain Admin за вечер. Хватило одной сервисной учётки с SPN и паролем, который не меняли с 2019 года. Kerberoasting, потом Golden Ticket, и домен захвачен. Защита смотрит на инфраструктуру как на схему. Атакующий видит в ней цепочку…

🔥7❤4👍1💯1

29 Sept 2026, 07:01 UTC≈1,110 views3 reactionsread 29 September 2026

🗓️ Расписание вебинаров на сегодня ⏰ 19:00 МСК - Безопасность в Angie 🔗 Регистрация и программа О вебинаре напомним за 5 минут до начала на этом канале. Также вы сможете зайти через личный кабинет. 🔥 Задать вопросы и обсудить детали можно в нашем чате

🔥3

28 Sept 2026, 12:17 UTC≈2,640 views7 reactionsread 2 October 2026
Photo

⏰ 3..2..1..Уже завтра Вася Озеров проведет первое занятие на интенсиве "Системный траблшутинг" Осталось несколько свободных мест. Интенсив в живом формате проводим всего один раз: если хочешь перейти от хаотичного угадывания причин сбоев к четкому трехшаговому алгоритму, который помогает быстро находить причину и устранять её, занимай место. ↘️ Занять место Что будет: 🟢 Живой формат: 6 вебинаров с Васей Озеровым …

❤5🔥2

27 Sept 2026, 17:56 UTC≈2,650 views19 reactionsread 2 October 2026

🔥 Как ИИ-агент работает под капотом: новое видео с Марком Кудрицким уже на канале Делимся записью открытого практикума. На нём подняли автономного агента Hermes, подключили LangFuse и посмотрели, что на самом деле уходит в LLM на каждый запрос. Краткий конспект👇🏼 🟢Агент = обёртка над моделью LLM сама ничего не запускает на компьютере. Она возвращает JSON с вызовом инструмента. Локальный Python-код (harness) разбира…

👍9🔥6❤4

26 Sept 2026, 17:59 UTC≈2,820 views68 reactionsread 2 October 2026

☕️ IT-сводка нескучных новостей: обновления ядра каждую неделю, взлом дорожной камеры, systemd собирает отчёты сам 🟢Ubuntu объявила о переходе на еженедельный выпуск обновлений ядра С 28 сентября Canonical переводит обновления ядра на перекрывающиеся двухнедельные циклы, из-за чего новое ядро выходит фактически каждую неделю. Количество CVE взорвалось, и старая схема перестала за ним успевать. Отложить апгрейд на с…

🔥59👍5❤4

24 Sept 2026, 14:12 UTC≈3,560 views10 reactionsread 2 October 2026

Интенсив «Системный траблшутинг» с Васей Озеровым стартует уже на следующей неделе, собрали ответы на частые вопросы и коротко рассказали, как всё будет. За 6 живых эфиров с Васей ты разберёшь путь запроса и пакета через всю систему: от сети в Linux до Kubernetes и мониторинга. Научишься находить причину сбоя по трёхшаговому алгоритму, разберёшь проблемы с MTU/MSS через tcpdump, настроишь лимиты cgroups против throt…

❤9👍1

Showing the 12 most recent of 91 posts we hold for @rebrain_devops. 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.

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 1 registered channel — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

ServerAdmin.ru
@srv_admin · 32,572
#1
Bash Days | Linux | DevOps
@bashdays · 23,634
#2
Мониторим ИТ
@monitorim_it · 8,542
#3
Ever Secure
@ever_secure · 4,728
#4
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,617
#5
k8s (in)security
@k8security · 13,151
#6
DevOps FM
@devops_fm · 5,282
#7
Слёрм
@slurmnews · 8,080
#8
DevOps | Вопросы собесов
@easy_devops · 5,560
#9
Devops Jobs — вакансии и резюме
@devops_jobs_feed · 21,917
#10
DevOps
@i_DevOps · 8,817
#11
Пятничный деплой
@count0_digest · 4,758
#12
DevSecOps Talks
@devsecops_weekly · 8,038
#13
Devops Bootcamp с Федосеевым
@devopsupgrade · 5,327
#14
Системный администратор
@i_odmin · 26,669
#15
Библиотека девопса | DevOps, SRE, Sysadmin
@devopsslib · 10,381
#16
KazDevOps
@DevOpsKaz · 6,867
#17
IT-KB 🤖
@ITKB_channel · 8,000
#18
BZD • Книги для программистов
@bzd_channel · 36,402
#19
/usr/bin
@usr_bin_linux · 4,901
#20
DevOps
@DevOPSitsec · 23,684
#21
DevOps Deflope News
@devops_deflope · 5,840
#22
Kubernetes и кот Лихачева
@Kubernetes_Likhachev · 4,779
#23
Admin Guides | Сисадмин
@admguides · 11,942
#24
ЗаТелеком 🌐
@zatelecom · 64,498
#25
Вокруг Kubernetes в VK
@k8s_vk · 4,318
#26
Selectel
@Selectel · 63,164
#27
Golang
@Golang_google · 40,461
#28
DeusOps
@deusops · 3,075
#29
BashMaster
@bash_help · 8,854
#30
infosec
@it_secur · 62,112
#31
SecurityLab.ru
@SecLabNews · 84,654
#32
Библиотека собеса по DevOps | вопросы с собеседований
@devops_interview_lib · 3,451
#33
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,557
#34
Social Engineering
@Social_engineering · 125,007
#35
Флант | Специалисты по DevOps и Kubernetes
@flant_ru · 2,181
#36
Библиотека Go-разработчика | Golang
@goproglib · 24,076
#37
Linux / Линукс
@linux_gram · 13,665
#38
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,092
#39
Yandex Cloud
@yandexcloudnews · 22,652
#40
Записки IT специалиста
@interface31 · 8,987
#41
Devops
@dev_ops_info · 2,187
#42
Linux Education
@linux_education · 11,122
#43
DevOps MemOps
@devops_memops · 6,319
#44
Библиотека задач по DevOps | тесты, код, задания
@devops_problems_lib · 3,013
#45
Network Warrior
@ntwrkchnnl · 3,689
#46
DevOps Factory
@devops_factory · 1,726
#47
Linux Academy
@linuxacademiya · 28,434
#48
Библиотека программиста
@proglibrary · 78,288
#49
Лига сисадминов
@sysodmins_league · 13,234
#50
Inside Yandex Cloud
@cloud_track · 8,301
#51
этогик // DevOps, Infrastructure, Productivity
@etogeek · 4,378
#52
DevOps для ДевоПсов
@devo_pes · 3,209
#53
DevOps Portal | Linux
@loose_code · 13,088
#54
linkmeup
@linkmeup_podcast · 17,412
#55
DevOps&SRE Library
@devopslibrary · 19,877
#56
Мир ИТ c Антоном Павленко
@worlditech · 7,299
#57
Записки админа
@SysadminNotes · 12,736
#58
The After Times
@theaftertimes · 16,799
#59
Useful Tools | Linux | GitOps | DevOps
@gitgate · 6,766
#60
DevOps community for love
@devopsforlove · 44,637
#61
Админим с Буквой
@bykvaadm · 6,420
#62
Хабр
@habr_com · 132,764
#63
Типичный Сисадмин
@sysodmins · 38,219
#64
opennet.ru
@opennet_ru · 15,730
#65
Linux
@linux_sup · 7,440
#66
Технологический Болт Генона
@tech_b0lt_Genona · 9,761
#67
Утечки информации
@dataleak · 119,057
#68
Минцифры России
@mintsifry · 234,926
#69
DOFH - DevOps from hell
@DOFH_ru · 3,779
#70
Rozetked
@rozetked · 672,965
#71
GARDEN | DevOps
@devopsgarden · 4,402
#72
addmeto
@addmeto · 71,835
#73
Вакансии по DevOps & SRE
@devopssjob · 4,467
#74
Zabbix Recipes
@zabbix_ru · 3,625
#75
Код.ру
@d_code · 406,147
#76
GitHub Community
@github · 155,991
#77
Job for Sysadmin & DevOps
@fordevops · 4,893
#78
Типичный программист
@tproger · 78,167
#79
MikroTik-сэнсэй
@mikrotik_sensei · 19,528
#80
CodeCamp
@codecamp · 180,482
#81
Николай Тузов
@ntuzov · 16,870
#82
Диджитализируй!
@t0digital · 28,475
#83
DevOps на минималках
@devopseri · 2,781
#84
SecAtor
@true_secator · 41,748
#85
Mikrotik Ninja
@mikrotikninja · 3,970
#86
Postgres Guru | Базы данных 💐
@pg_guru · 2,870
#87
Sys-Admin InfoSec
@sysadm_in_channel · 12,946
#88
IT Юмор
@ithumor · 60,568
#89
Сетевой архитектор
@net_arch · 7,414
#90
Vasiliy Ozerov
@vasiliyinside · 3,289
#91
Network Admin
@networkadm · 12,380
#92
Эксплойт
@exploitex · 2,048,279
#93
Бэкдор
@whackdoor · 1,590,187
#94

Read from Telegram’s recommendation API, most recently 9 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.

Devops Jobs — вакансии и резюме
@devops_jobs_feed · 21,917
Telegram ranks this channel #4 of 95 here — alongside 94 others — read 22 September 2026
Selectel
@Selectel · 63,164
Telegram ranks this channel #7 of 96 here — alongside 95 others — read 21 August 2026
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,617
Telegram ranks this channel #8 of 90 here — alongside 89 others — read 18 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,634
Telegram ranks this channel #9 of 94 here — alongside 93 others — read 18 September 2026
DevOps community for love
@devopsforlove · 44,637
Telegram ranks this channel #13 of 95 here — alongside 94 others — read 9 September 2026
ServerAdmin.ru
@srv_admin · 32,572
Telegram ranks this channel #14 of 96 here — alongside 95 others — read 5 September 2026
BZD • Книги для программистов
@bzd_channel · 36,402
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 1 September 2026
Системный администратор
@i_odmin · 26,669
Telegram ranks this channel #24 of 89 here — alongside 88 others — read 12 September 2026
DevOps
@DevOPSitsec · 23,684
Telegram ranks this channel #25 of 90 here — alongside 89 others — read 18 September 2026
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,557
Telegram ranks this channel #43 of 85 here — alongside 84 others — read 13 September 2026
MikroTik-сэнсэй
@mikrotik_sensei · 19,528
Telegram ranks this channel #49 of 92 here — alongside 91 others — read 1 October 2026
IT STAND
@ITSTAND_ORG · 155,546
Telegram ranks this channel #55 of 98 here — alongside 97 others — read 9 September 2026
DevOps&SRE Library
@devopslibrary · 19,877
Telegram ranks this channel #56 of 94 here — alongside 93 others — read 30 September 2026
Pythonist.ru - образование по питону
@pythonist_ru · 24,046
Telegram ranks this channel #78 of 82 here — alongside 81 others — read 17 September 2026
Linux для чайника
@os_linux_ru · 19,601
Telegram ranks this channel #80 of 87 here — alongside 86 others — read 1 October 2026

This channel appears in 15 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 26 September 2026 — this entry's latest reading, not the date you are reading this.

“DevOps by REBRAIN” (@rebrain_devops), 28,873 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/rebrain_devops.

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.