Telegram RegisterThe public register of Telegram
Telegram profile photo for ⚠️ Zapret KVN (объявления & обновления) [тех. работы]

Channel

⚠️ Zapret KVN (объявления & обновления) [тех. работы]

@vpndiscordyooutube

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

7,731subscribers

+167 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003285913340
TypeChannel
Username@vpndiscordyooutube
CreatedBetween 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/vpndiscordyooutube

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

7,5647,7357,649.57 August 2026 — 7,564 subscribers7 August 2026 — 7,564 subscribers8 August 2026 — 7,570 subscribers11 August 2026 — 7,578 subscribers15 August 2026 — 7,608 subscribers18 August 2026 — 7,620 subscribers20 August 2026 — 7,629 subscribers24 August 2026 — 7,652 subscribers27 August 2026 — 7,667 subscribers31 August 2026 — 7,663 subscribers2 September 2026 — 7,683 subscribers7 September 2026 — 7,710 subscribers11 September 2026 — 7,735 subscribers15 September 2026 — 7,731 subscribers7,7317 August 202615 September 2026
14 measurements spanning 39 days, net +167. 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 7,538–7,761 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 16:177,731-4
11 Sept 2026, 15:557,735+25
7 Sept 2026, 02:147,710+27
2 Sept 2026, 20:567,683+20
31 Aug 2026, 00:157,663-4
27 Aug 2026, 19:357,667+15
24 Aug 2026, 21:237,652+23
20 Aug 2026, 23:567,629+9
18 Aug 2026, 00:077,620+12
15 Aug 2026, 02:567,608+30
11 Aug 2026, 11:247,578+8
8 Aug 2026, 06:417,570+6
7 Aug 2026, 18:167,564no change
7 Aug 2026, 18:077,564first reading

Engagement

117 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 7,731 subscribers
Avg views / post
1,050
22 posts measured
Reaction rate
1.58%
reactions ÷ views · ER floor
Posts in window
22
of 117 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 28 August 2026
Posts held117 (6 August 202628 August 2026)
Views total23,157
Reactions total366
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 21:04 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

2,397 reactions across 117 posts, in 50 distinct kinds. The most used accounts for 30.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
72230.1%
👍34014.2%
🔥2299.55%
🥰1907.93%
😭1024.26%
🤝793.30%
👀753.13%
🤔743.09%
❤‍🔥733.05%
😁652.71%
🙏351.46%
🍾301.25%
💋281.17%
💘241.00%
😍241.00%
😢230.96%
🕊220.918%
🤣210.876%
🤯210.876%
🤪200.834%
30 further kinds2008.34%

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

Measured over the 117 most recent posts we hold, published 6 August 2026 to 28 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.

Recent posts

28 Aug 2026, 20:56 UTC77 views2 reactionsread 28 August 2026

Продолжаем укреплять надёжность Zapret VPN. Очередь выдачи ключей Hysteria 2-подписок теперь под постоянным автоматическим контролем: если сборка ключей остановится или появятся записи, требующие вмешательства, система сама откроет инцидент на статус-странице. Следить за состоянием можно на status.zapret.moe — разделы «Системы» и «Инциденты».

👍2

28 Aug 2026, 20:27 UTC285 views6 reactionsread 28 August 2026

Вернули в строй сервер Hysteria 2 в Казахстане (Астана) — он снова принимает подключения, и всем подписчикам, ждавшим этот регион, автоматически выданы ключи: сервер сам появился в вашей единой Hysteria 2-подписке, ничего обновлять вручную не нужно. Проверить свою ссылку можно командой /hysteria2_url в боте, а состояние всех систем — на status.zapret.moe.

3👍2🔥1

28 Aug 2026, 20:20 UTC323 views5 reactionsread 28 August 2026

Продолжаем улучшать Zapret VPN. Навели порядок в единой Hysteria 2-подписке: режим «рекомендованные серверы» теперь сам подбирает только реально доступные вам площадки — у части пользователей набор автоматически дополнился до полного. Публичная страница status.zapret.moe/queues стала честнее: очередь показывает только настоящую работу, а серверы, недоступные тарифу или временно закрытые на обслуживание, вынесены в о

3👍1🔥1

28 Aug 2026, 19:01 UTC619 views7 reactionsread 28 August 2026

Эта часть как обычно самое трудная потому что тяжело доказать что есть сканеры РКН, а что — нет

7

28 Aug 2026, 18:59 UTC616 views7 reactionsread 28 August 2026

Российское приложение на устройстве │ ├─ клиентское правило сработало │ └─ DIRECT с домашнего/мобильного IP │ └─ клиентское правило не сработало └─ трафик пришёл на VPN-ноду │ ├─ обычный сайт/backend приложения │ └─ WARP → сайт видит Cloudflare IP │

7

28 Aug 2026, 18:57 UTC586 views11 reactionsread 28 August 2026

На данный момент мы решили пропускать РФ сервера через варп — это надежно защитит выходные айпи нод и позволит пользоваться РФ сайтами если ВДРУГ все таки клиент настроен неправильно и РФ приложение все таки удалось подключиться к нашей ноде. Это не защищает сервер от блокировки но улучшает юзабилити пользователя Это возможно благодаря новой архитектуре: vpnbot_node_services/ ├── manifest.json ├── contracts/ │ ├─

10👍1

28 Aug 2026, 18:38 UTC654 views5 reactionsread 28 August 2026

Починили редкую, но неприятную проблему Mihomo-подписок: если среди ключей пользователя оказывался один «застрявший», сервис отказывался отдавать весь профиль, и приложение показывало «Ошибка сети». Теперь такой ключ временно исключается, а остальная подписка продолжает работать; все затронутые ключи восстановлены. Дополнительно статус-страница status.zapret.moe теперь показывает такие сбои сразу — мы узнаём о них

🥰31👍1

28 Aug 2026, 16:45 UTC878 views16 reactionsread 28 August 2026

Довели до ума страницу состояния status.zapret.moe/queues: теперь каждая очередь честно пишет, что именно у неё не в порядке и где искать подробности — вместо загадочного жёлтого кружка. Заодно устранили зависание фоновой выдачи VLESS-ключей: застрявшие задания снова завершаются автоматически.

10🥰3🍾1👍1🕊1

28 Aug 2026, 14:53 UTC≈1,050 views18 reactionsread 28 August 2026

В данный момент мы разрабатываем новую цепочку из нескольких серверов но нам потребуется время. Подробности рассказать (по понятным причинам) не можем

13👍5

28 Aug 2026, 14:29 UTC≈1,090 views19 reactionsread 28 August 2026

На данный момент мы не можем заменить сервера так как чиним внутреннюю инфраструктуру. Это две независимые проблемы. План для вас: Рекомендуем начать с влесса. Если влесс весь не работает продурить запретом и снова попробовать весь влесс. Только после этого пробовать wireguard. Ковыряться с этим можно целый день и шанс найти что-то рабочее в любых случаях 99% (кроме зоны БС)

😭12👌3🥴3🤗1

28 Aug 2026, 12:18 UTC≈1,190 views25 reactionsread 28 August 2026

Инфраструктурный инцидент DE compute node failure Актуальные обновления об инфраструктурном инциденте этого сервера. Статус Устраняется Начало 21.08.2026 06:28:57 Оперативные обновления Хронология инцидента 1 Здравствуйте, К сожалению, мы столкнулись с аварийной ситуацией в дата-центре Германии из-за которой вышел из строя сервер на котором находилась ваша услуга. К сожалению, данные безвозвратно утрачены. Сейчас мы

🤔10😱5🥱4🤯3🙈3

28 Aug 2026, 11:53 UTC≈1,240 views11 reactionsread 28 August 2026
Photo

Проблемы с влесс подпиской теперь видно и нам и вам Раньше очереди могли скрываться из-за чего не понятно устранены все ошибки или ещё нет. Теперь будем добивать её до зелёного статуса. Насколько мы понимаем с михомо и хистерией проблем нет (первая очередь не создает ключи, вторая создает быстро)

👍83

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

Mentions

Named by 2 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.

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

“⚠️ Zapret KVN (объявления & обновления) [тех. работы]” (@vpndiscordyooutube), 7,731 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/vpndiscordyooutube.

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.