Telegram RegisterThe public register of Telegram

Channel

is*hosting

@ishosting

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

6,627subscribers

-12 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001033708290
TypeChannel
Username@ishosting
Created4 March 2016measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ishosting

Growth

6,6276,6396,6335 August 2026 — 6,639 subscribers6 August 2026 — 6,639 subscribers6 August 2026 — 6,638 subscribers9 August 2026 — 6,634 subscribers12 August 2026 — 6,627 subscribers5 August 202612 August 2026
5 measurements spanning 6 days, net -12. 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 6,625–6,641 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:396,627-7
9 Aug 2026, 02:016,634-4
6 Aug 2026, 09:436,638-1
6 Aug 2026, 03:196,639no change
5 Aug 2026, 19:046,639first reading

Engagement

20 posts held, back to 7 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
47.0%
avg views ÷ 6,627 subscribers
Avg views / post
3,120
2 posts measured
Reaction rate
0.433%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 19 July 2026
Posts held20 (7 November 202519 July 2026)
Views total6,230
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:57 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

1,357 reactions across 20 posts, in 15 distinct kinds. The most used accounts for 23.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍32323.8%
23417.2%
🔥23117.0%
😱18813.9%
😁1128.25%
🎉674.94%
🤔513.76%
custom 5204036045192046230473.46%
😢322.36%
👎312.28%
🤩100.737%
🤬100.737%
🥰90.663%
👏70.516%
🤯50.368%

Custom emoji. One row above is a 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 count beside it isTelegram’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 20 of the 20 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,357reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 7 November 2025 to 19 July 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
25
across the posts below
Posts paid on
8
of 20 we hold a reading for · 40%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ishosting. 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 20 most recent posts we hold for this entry, published 7 November 2025 to 19 July 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

19 Jul 2026, 07:34 UTC≈3,180 views12 reactionsread 12 August 2026

⚠️ Критическая уязвимость в WordPress — проверьте свой сайт 17 июля WordPress выпустил экстренные обновления 6.9.5 и 7.0.2, закрывающие уязвимость *wp2shell* — цепочку в ядре CMS, которая позволяет выполнять код на сервере *без авторизации и без единого плагина*. Уязвимы стандартные установки версий 6.9.0 – 7.0.1 Случаев эксплуатации пока не зафиксировано, но проблема настолько серьёзна, что WordPress впервые за до

custom 52040360451920462306🔥3🤔2😁1

18 Jul 2026, 09:33 UTC≈3,050 views15 reactionsread 12 August 2026
Forwarded from @ZerodayAlertPhoto

Новые уязвимости обнаружены в NGINX Plus и Open Source Компания F5 обнаружила три уязвимости в NGINX Plus и NGINX Open Source, самая опасная из них получила оценку 9.2 из 10. Она связана с обработкой определённых запросов и в худшем случае может позволить злоумышленнику выполнить произвольный код на сервере. Две другие уязвимости с оценками 8.8 и 8.3 позволяют злоумышленникам получать фрагменты данных из памяти сер

🔥9😱51

24 Jun 2026, 13:30 UTC≈5,270 views46 reactionsread 12 August 2026
Photo

Hermes Agent, OpenClaw, n8n и Coolify (который мы спонсируем кстати) теперь предустановлены на is*hosting VPS от $10.19/месяц. Hermes (вот гайд) OpenClaw (гайд) n8n (гайд) - от $5.94 Coolify (гайд) Запускаются и настраиваются за несколько минут.

😁22👍13🎉4custom 52040360451920462303🔥21👎1

12 May 2026, 18:24 UTC≈8,660 views41 reactions1 Starread 12 August 2026

🐧 В Linux обнаружена критическая уязвимость «Dirty Frag», позволяющая получить root-доступ. Исследователь Hyunwoo Kim опубликовал детали новой LPE-уязвимости после срыва embargo. Проблема затрагивает ядра Linux начиная примерно с 2017 года и уже сопровождается публичным PoC-эксплойтом. Источник «Dirty Frag» — это цепочка из двух багов в подсистемах xfrm-ESP и RxRPC ядра Linux. Локальный пользователь может мгновенно

👍246custom 52040360451920462306🔥3😁1😱1

1 May 2026, 15:48 UTC≈8,080 views46 reactionsread 12 August 2026

⚠️ В cPanel нашли дыру по которой на сервер можно зайти без пароля. Касается всех версий cPanel, WHM и DNSOnly начиная с 11.40. Уязвимость обходит проверку подлинности — то есть учётка для входа, в общем-то, не нужна. Патчи уже есть для 11.86, 11.110, 11.118, 11.126, 11.130, 11.132, 11.134, 11.136 и WP Squared 136.1.7. Для юзеров CentOS 6 / CloudLinux 6 выкатили 110.0.103 отдельным апдейтом. Если автообновления вк

👍21🔥86🤩6😱3custom 52040360451920462302

30 Apr 2026, 12:50 UTC≈7,850 views86 reactionsread 12 August 2026

⚠️ Срочно: обновите ядро Linux Раскрыта критическая уязвимость ядра Linux CVE-2026-31431 («Copy Fail», CVSS 7.8). Затронуты практически все дистрибутивы с ядрами 2017+ — Ubuntu, Debian, RHEL, Alma, Rocky, SUSE, Amazon Linux. Локальный непривилегированный пользователь получает root через 10-строчный Python-скрипт, редактирующий PageCache любого файла, включая setuid-бинарники. Без race-условий, без подбора смещений.

48🔥18👍12custom 52040360451920462305🤩2👎1

25 Feb 2026, 07:52 UTC≈9,140 views9 reactionsread 12 August 2026
Forwarded from @ZerodayAlert

Почтовый клиент Roundcube стал вектором активных кибератак CISA предупредило о двух уязвимостях в Roundcube Webmail — популярном почтовом клиенте, широко используемом в корпоративных сетях. Обе бреши уже применяются в реальных атаках, что и послужило основанием для обновления списка известных активно эксплуатируемых уязвимостей. Первая — CVE-2025-49113 с оценкой CVSS 9.9 — позволяет авторизованному пользователю вып

custom 520403604519204623054

5 Feb 2026, 11:03 UTC≈10,600 views46 reactions3 Starsread 12 August 2026
Photo

Теперь на is*hosting VPS можно развернуть и запустить Clawdbot Moltbot OpenClaw Как запустить (за 2–3 минуты): • Купить VPS (Medium или выше); • Выберите “Ubuntu 22 – Clawdbot (OpenClaw)”; • SSH • Запустите openclaw onboard и подключите мессенджеры. 2 GB RAM хватит для чатов; 4 GB+ рекомендованы для работы в браузере и автоматизации задач. Тут подробности о том, что это за бот и зачем он нужен

🔥21😁9👍85custom 52040360451920462303

9 Jan 2026, 14:32 UTC≈11,300 views27 reactionsread 12 August 2026
Forwarded from @tomhunterPhoto

#news В n8n, платформе для автоматизации рабочих процессов, очередная уязвимость на 10 из 10, цепочка ведёт к RCE и произвольной записи файлов. Это уже четвёртая критическая CVE, раскрытая в n8n за пару недель. Свежайшая получила название Ni8mare, раскрытая днём ранее — N8scape, там же затесалась ещё одна безымянная десяточка. Как водится, если не дать уязвимости запоминающееся имя, шансы того, что поднимется хайп и

🔥165🤔2🤯2🤬1😱1

30 Dec 2025, 14:42 UTC≈10,700 views153 reactions8 Starsread 12 August 2026
Photo

Желаем стабильной и предсказуемой инфраструктуры в 2026, независимо от того, где она развёрнута! (если она не такая, то вы знаете что делать) Короч, берегите себя, пейте больше воды, и не забудьте про бэкапы. С Наступающим, и пусть он будет норм!

98🎉36🔥12👍6😱1

5 Dec 2025, 09:19 UTC≈12,700 views110 reactionsread 12 August 2026
Forwarded from @issomething_ruPhoto

Cloudflare опять упал

😱69😢14👎9🥰6😁5custom 52040360451920462304🤩2🎉1

4 Dec 2025, 13:39 UTC≈11,800 views51 reactionsread 12 August 2026

React2Shell: критическая уязвимость в RSC (CVE-2025-55182) В экосистеме React и Next.js стало известно о критической уязвимости максимального уровня (CVSS 10), получившей название React2Shell. Она затрагивает React Server Components и может привести к выполнению произвольного кода без аутентификации. CVE-2025-55182 была раскрыта вчера вечером. По данным Unit 42, под риском почти миллион серверов. По оценкам Wiz, уя

😱28👍86🔥5🤔2😁2

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 370,212 of 1,169,250entries 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.

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

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

“is*hosting” (@ishosting), 6,627 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ishosting.

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.