4 measurements spanning 9 days, net -982. 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 349–1,683 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
16 Aug 2026, 16:48
547
+44
8 Aug 2026, 08:36
503
-1,026
7 Aug 2026, 09:32
1,529
no change
7 Aug 2026, 09:18
1,529
first reading
Engagement
22 posts held, back to 2 August 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
17.5%
avg views ÷ 547 subscribers
Avg views / post
95.7
22 posts measured
Reaction rate
3.27%
reactions ÷ views · ER floor
Posts in window
22
of 22 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. It is computed over the 10 of 22 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
22 (2 August 2026 – 7 August 2026)
Views total
2,106
Reactions total
33
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 18:09 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.
Reaction mix
33 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 75.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
25
75.8%
😁
5
15.2%
🔥
3
9.09%
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 10 of the 22 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 33reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 2 August 2026 to 7 August 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.
📘 Записка №020
🔹 Ситуация
На Linux-шлюзе уже открытые соединения работают, но новые TCP-сессии создаются через раз. В журнале появляется сообщение:
nf_conntrack: table full, dropping packet
🔹 Почему это произошло
Таблица conntrack достигла значения nf_conntrack_max. Ядро больше не может создавать записи для новых соединений, поэтому первые пакеты сессий отбрасываются. Частая причина — всплеск коротких соединений, ск…
📘 Записка №019
🔹 Российские вендоры сетевого оборудования: кого выбрать в 2026 году?
Ещё несколько лет назад вопрос выбора сетевого оборудования обычно сводился к Cisco, Huawei, Juniper или HPE. Сегодня ситуация изменилась. Всё больше компаний переходят на российских производителей, а в государственных организациях это уже стало стандартом.
Но насколько российское оборудование готово заменить привычных зарубежных …
Коллеги, сегодня хотим порекомендовать канал, который сами читаем с удовольствием.
Если вам интересны не только команды в CLI, но и то, как устроена работа сетевой инфраструктуры в крупных компаниях, рекомендуем заглянуть в канал «Будни сетевика».
Его ведёт Дмитрий Ипатов. Сейчас он уже больше занимается управлением командой и развитием сетевой инфраструктуры, чем настройкой оборудования своими руками. Но именно по…
📘 Записка №018
🔹 Ситуация
После ошибки на стороне провайдера маршрутизатор получил сотни тысяч BGP-префиксов вместо ожидаемых нескольких сотен. Память и CPU резко выросли, а сеть начала терять пакеты.
🔹 Почему это произошло
Без ограничения количества принимаемых маршрутов BGP-сосед может передать полную таблицу или ошибочный анонс. Механизм Maximum Prefix разрывает сессию либо выдаёт предупреждение после достижения…
📘 Записка №017
🔹 Ситуация
После включения vlan-filtering=yes на MikroTik пропал доступ к WinBox и SSH, хотя физический порт активен, а клиент находится в правильном VLAN.
🔹 Почему это произошло
В Bridge VLAN Table забыли добавить сам bridge как tagged-порт. В RouterOS bridge представляет CPU-порт устройства. Если его нет в VLAN, трафик проходит между физическими портами, но не попадает к IP-адресу самого маршрутиза…
Что произойдет, когда клиент отправит DHCP Discover?
R1 автоматически преобразует широковещательный DHCP Discover в unicast и отправит его серверу.11%
DHCP Discover останется в локальном широковещательном домене, не достигнет DHCP-сервера.67%
R2 самостоятельно обнаружит DHCP Discover и передаст его серверу.0%
DHCP-сервер ответит через маршрутизаторы без необходимости использовать DHCP Relay.22%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 22 posts we hold for @Network_history_NFA. 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.
Polls
The 5 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.
OSPF обнаружит отказ только после истечения Dead Interval (по умолчанию около 40 секунд).0%
BFD быстро обнаружит отказ, после чего OSPF практически сразу разорвет соседство и пересчитает маршр81%
BFD самостоятельно перестроит таблицу маршрутизации, OSPF в этом процессе не участвует.10%
OSPF и BFD нельзя использовать одновременно.10%
Shares as published, totalling 101%. 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 22 most recent posts we hold, published 2 August 2026 to 7 August 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.
Citation-graph rank
Citation-graph rank — 1,303,068 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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 16 August 2026 — this
entry's latest reading, not the date you are reading this.
“📖Записки сетевика | Сети для всех” (@Network_history_NFA), 547 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Network_history_NFA.
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.