Telegram RegisterThe public register of Telegram
Telegram profile photo for HERAKS

Channel

HERAKS

@heraks2net

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

10,777subscribers

+71 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001447216015
TypeChannel
Username@heraks2net
DescriptionХЕРАКС: Сбои и фейлы
Created22 January 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/heraks2net

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 16 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

10,68510,78710,7365 August 2026 — 10,706 subscribers6 August 2026 — 10,706 subscribers6 August 2026 — 10,704 subscribers7 August 2026 — 10,701 subscribers8 August 2026 — 10,700 subscribers9 August 2026 — 10,698 subscribers11 August 2026 — 10,696 subscribers12 August 2026 — 10,687 subscribers13 August 2026 — 10,685 subscribers14 August 2026 — 10,699 subscribers16 August 2026 — 10,701 subscribers17 August 2026 — 10,695 subscribers18 August 2026 — 10,691 subscribers19 August 2026 — 10,760 subscribers21 August 2026 — 10,757 subscribers22 August 2026 — 10,758 subscribers24 August 2026 — 10,754 subscribers25 August 2026 — 10,752 subscribers26 August 2026 — 10,751 subscribers27 August 2026 — 10,748 subscribers29 August 2026 — 10,746 subscribers30 August 2026 — 10,745 subscribers31 August 2026 — 10,743 subscribers1 September 2026 — 10,742 subscribers2 September 2026 — 10,739 subscribers4 September 2026 — 10,735 subscribers7 September 2026 — 10,769 subscribers10 September 2026 — 10,778 subscribers12 September 2026 — 10,779 subscribers13 September 2026 — 10,775 subscribers15 September 2026 — 10,772 subscribers17 September 2026 — 10,771 subscribers27 September 2026 — 10,767 subscribers4 October 2026 — 10,749 subscribers9 October 2026 — 10,787 subscribers13 October 2026 — 10,751 subscribers14 October 2026 — 10,749 subscribers15 October 2026 — 10,746 subscribers18 October 2026 — 10,743 subscribers19 October 2026 — 10,738 subscribers21 October 2026 — 10,750 subscribers22 October 2026 — 10,781 subscribers23 October 2026 — 10,786 subscribers24 October 2026 — 10,785 subscribers25 October 2026 — 10,784 subscribers27 October 2026 — 10,785 subscribers28 October 2026 — 10,787 subscribers30 October 2026 — 10,786 subscribers1 November 2026 — 10,785 subscribers2 November 2026 — 10,786 subscribers4 November 2026 — 10,787 subscribers5 November 2026 — 10,785 subscribers6 November 2026 — 10,784 subscribers7 November 2026 — 10,783 subscribers9 November 2026 — 10,781 subscribers10 November 2026 — 10,777 subscribers10,7775 August 202610 November 2026
56 measurements spanning 97 days, net +71. 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 10,670–10,802 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
10 Nov 2026, 18:2110,777-4
9 Nov 2026, 08:4710,781-2
7 Nov 2026, 22:4010,783-1
6 Nov 2026, 22:4010,784-1
5 Nov 2026, 21:5910,785-2
4 Nov 2026, 20:4710,787+1
2 Nov 2026, 23:0410,786+1
1 Nov 2026, 02:2010,785-1
30 Oct 2026, 06:4010,786-1
28 Oct 2026, 02:3110,787+2
27 Oct 2026, 05:2710,785+1
25 Oct 2026, 03:5710,784-1
24 Oct 2026, 05:1710,785-1
23 Oct 2026, 07:1610,786+5
22 Oct 2026, 04:3010,781+31
21 Oct 2026, 01:4010,750+12
19 Oct 2026, 23:4410,738-5
18 Oct 2026, 21:0710,743-3
15 Oct 2026, 14:5710,746-3
14 Oct 2026, 15:4110,749first reading

Engagement

60 posts held, back to 3 April 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
82.0%
avg views ÷ 10,777 subscribers
Avg views / post
8,840
16 posts measured
Reaction rate
0.701%
reactions ÷ views · ER floor
Posts in window
16
of 60 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 9 November 2026
Posts held60 (3 April 2026 – 9 November 2026)
Views total141,480
Reactions total992
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 10:08 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
396
Links
128

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

4,202 reactions across 58 posts, in 10 distinct kinds. The most used accounts for 23.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣1,00223.8%
🫡87720.9%
😢70516.8%
😱44210.5%
🤬3458.21%
🥱3408.09%
🤡3287.81%
💩962.28%
👎340.809%
🤮330.785%

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

Measured over the 60 most recent posts we hold, published 3 April 2026 to 9 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 60 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @heraks2net. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 60 most recent posts we hold for this entry, published 3 April 2026 to 9 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 16 posts held from the last 30 days (12.5%) 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).

9 Nov 2026, 16:43 UTC≈3,900 views14 reactionsread 11 November 2026

🟠 Make.com (make.com) Вендор сообщает о проблеме у внешнего провайдера: часть страниц сайта make.com, включая главную (www.make.com), не загружается и показывает пустую страницу. Платформа Make и выполнение сценариев, а также страницы вроде make.com/integrations не затронуты. Наших замеров пока нет, подтверждение основано на заявлении вендора. Начало инцидента (по данным вендора): 09.11.2026 17:34 (CET) Вендор об…

🥱14

2 Nov 2026, 10:44 UTC≈8,000 views65 reactionsread 11 November 2026
Forwarded from @tass_agency

В работе каршеринга BelkaCar произошел масштабный сбой из-за аварии у ИТ-провайдера, сообщили в пресс-службе сервиса.

🤣24😢24🫡14🥱3

2 Nov 2026, 07:10 UTC≈7,980 views75 reactionsread 11 November 2026
Photo

Бегет взломан не работает. https://t.me/zatelecom/34472

😢35🤣25🫡12🥱2👎1

26 Oct 2026, 14:16 UTC≈11,000 views58 reactionsread 11 November 2026
Photo

У Телеграм проблемы глобально. (Блин, после продажи Downdetector стал невозможно

😢40🥱7🤣6🤮2😱2🤡1

22 Oct 2026, 17:59 UTC≈12,300 views28 reactionsread 11 November 2026

🟠 Cloudflare: Build for the agent era (cloudflare.com) Вендор зафиксировал сбой доставки audit-логов для WARP API и зависимых сервисов Zero Trust. У части клиентов логи приходят с задержкой или не приходят вовсе. Причина — нехватка мощности во внутреннем data pipeline в регионе PDX. Вендор применил меры по снижению влияния, пайплайн частично восстановлен, работы продолжаются. Затронутые компоненты: Audit Logs, Zer…

😢17😱5🫡4🤬1🥱1

22 Oct 2026, 10:13 UTC≈9,730 views21 reactionsread 11 November 2026

✅ Scaleway (scaleway.com) Сервис восстановлен частично. По заявлению вендора: сайт BookMyName, вебмейл и RDAP-сервисы снова работают. Сервис редиректов всё ещё недоступен — вендор сообщает, что требуется дополнительное расследование перед восстановлением. Причина сбоя вендором не названа. Наша измеренная длительность: 18 часов и 55 минут Длительность по заявлению вендора: 18 часов и 56 минут

🫡19🥱2

21 Oct 2026, 14:33 UTC≈8,870 views102 reactionsread 11 November 2026

На сколько мне известно, Web-архив тоже на PHP был написан

🫡64😢23🤣11😱3🥱1

21 Oct 2026, 14:32 UTC≈8,870 views46 reactionsread 11 November 2026

🔴 Internet Archive (archive.org) Сервис недоступен. Все 6 наших зондов (регионы AU, BR, DE, EU, SG, US) фиксируют отказ — соединение по tcp не устанавливается, ошибка timed out. Вендор официальных заявлений о сбое не делал. Сообщение основано на данных наших зондов — проблема наблюдается широко, по нескольким независимым точкам, что указывает на вероятный глобальный характер сбоя. Затронуты пользователи, пытающиес…

😱34🫡7🤮2😢2🥱1

21 Oct 2026, 14:19 UTC≈7,890 views23 reactionsread 11 November 2026

🔴 Scaleway (scaleway.com) Вендор сообщает об экстренных технических работах: все сервисы BookMyName недоступны. Причина — критическая уязвимость в PHP (CVE-2026-109618, CVE-2026-109619, CVSS 9.2), позволяющая удалённое выполнение кода без аутентификации. Полного патча пока нет, поэтому BMN отключили в качестве превентивной меры на время обновления PHP. Касается пользователей BookMyName (регистрация и управление до…

🫡18😱4🥱1

21 Oct 2026, 13:19 UTC≈6,940 views32 reactionsread 11 November 2026
Photo

Собственно, причины. Скриншот перевод с немецкого

🫡30🤣1😱1

21 Oct 2026, 13:17 UTC≈6,760 views19 reactionsread 11 November 2026

🟣 DENIC (denic.de) Статус-страница вендора заявляет, что всё работает штатно. Однако по данным наших замеров сервис недоступен со всех 6 проголосовавших зондов (регионы: AU, BR, DE, EU, SG, US). Доступных регионов нет. Пример ошибки: http: bad status line Расхождение может объясняться несколькими причинами: запаздыванием обновления статус-страницы вендора, региональной блокировкой или локальным сетевым сбоем на с…

🫡14😱4🥱1

21 Oct 2026, 11:01 UTC≈6,360 views47 reactionsread 11 November 2026

✅ Google Public DNS (dns.google) Сервис восстановлен. По данным вендора, инцидент в регионе europe-west2 длился 7ч 52м и затрагивал 38+ продуктов (AlloyDB, Apigee, BigQuery Data Transfer Service и др.), сейчас статус — Available. Наши зонды фиксировали недоступность дольше — 1 день 1 час и 59 минут. Расхождение в длительности может говорить о том, что для части пользователей или регионов проблема сохранялась после …

🫡35🤣8🥱3😢1

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

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 4 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.

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.

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.

Типичный Сисадмин
@sysodmins · 40,818
Telegram ranks this channel #71 of 93 here — alongside 92 others — read 31 August 2026
Утечки информации
@dataleak · 117,768
Telegram ranks this channel #73 of 83 here — alongside 82 others — read 14 August 2026
Телекоммуналка
@telecommunal · 43,858
Telegram ranks this channel #77 of 93 here — alongside 92 others — read 28 August 2026
Roskomsvoboda
@roskomsvoboda · 40,498
Telegram ranks this channel #78 of 96 here — alongside 95 others — read 29 August 2026
#энерголикбез
@operby · 35,892
Telegram ranks this channel #84 of 85 here — alongside 84 others — read 2 September 2026
Игромир
@Igromir_cloud · 57,278
Telegram ranks this channel #85 of 89 here — alongside 88 others — read 22 August 2026

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

“HERAKS” (@heraks2net), 10,777 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/heraks2net.

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.