Sorry for taking long down time, most of service now back online and we are still working on couple of more services and servers. We will later explain details of this incident on website Thanks for being patient SiteJungle Team

Channel
SiteJungle - Hosting
@SiteJungle
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
97subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001664083544 |
|---|---|
| Type | Channel |
| Username | @SiteJungle |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/SiteJungle |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 22:23 | 97 | -1 |
| 9 Aug 2026, 11:45 | 98 | no change |
| 7 Aug 2026, 07:01 | 98 | first reading |
Engagement
19 posts held, back to 12 September 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 21.1%
- avg views ÷ 97 subscribers
- Avg views / post
- 20.5
- 2 posts measured
- Reaction rate
- 9.09%
- reactions ÷ views · ER floor
- Posts in window
- 2
- of 19 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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 19 (12 September 2023 – 5 August 2026) |
| Views total | 41 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 11:45 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
71 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 46.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 33 | 46.5% | |
| 🔥 | 15 | 21.1% | |
| ❤ | 13 | 18.3% | |
| 👎 | 4 | 5.63% | |
| 🤩 | 4 | 5.63% | |
| 😱 | 1 | 1.41% | |
| 🤔 | 1 | 1.41% |
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 17 of the 19 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 12 September 2023 to 5 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
⚠️⚠️ Currently we have down issue on all our services even our main website, please be patient while we are checking
👍2
USDT payments now support the BEP20 network as well. All clients can pay invoices using USDT across TRC20, Polygon, and BEP20 networks. If you need any assistance, feel free to open a support ticket anytime. SiteJungle Regards
🔥3
Hi According to the official cPanel report (LINK), we are currently performing immediate maintenance on our shared hosting services. If you experience any downtime, please be patient while we apply necessary fixes, updates, and security improvements. If you are using a VPS or dedicated server that is not managed by us, we strongly recommend applying these updates as soon as possible. You can always send us ticket i…
👍5
Happy New Year 🎉 SiteJungle 2026 Unbreakable, stronger than before unstoppable… we will be always there @SiteJungle
🔥3👎1
⚠️ Currently, Cloudflare is experiencing issues. If your website is showing an Internal Server Error (Error Code 500), this is related to Cloudflare and not our servers. You can check the status here: https://www.cloudflarestatus.com/ @SiteJungle
❤3
⚠️ Due to legal complications related to the domains on our bulletproof services, we are compelled to adjust our domain registration prices. As a result, domain costs will increase because these legal matters have created additional expenses for us. @SiteJungle
👍2🤔1😱1
The issues with the domain have been temporarily resolved. Be aware that domain prices will be adjusted shortly, with an anticipated increase. @SiteJungle
❤2
Please note that new domain registrations are currently disabled. All payments made for pending domain orders have already been refunded as credits to your account. You Can still order hosts or other services, only Domain registration for now disabled and you can use your domains from other registrar. Thank you for your understanding and support. Announcements @SiteJungle
👍4
All issues for now resolved for now Please check your domains, and let us know if you encounter any further issues @SiteJungle
❤5
Update: Most of the issues have been resolved, and many domains are now back online. Please check your domains, and let us know if you encounter any further issues.
#Announcement 📢 We are currently experiencing an issue with one of our DMCA-ignored systems, which has caused downtime for some domains. Our team is working diligently to resolve this as quickly as possible. We appreciate your patience and understanding during this time. Please note that all servers remain operational, and you can still access your cPanel and other services without any issues. We will update here so…
👍5
Showing the 12 most recent of 19 posts we hold for @SiteJungle. 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.
Citation-graph rank
Citation-graph rank — 547,272 of 1,629,497 entries 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
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“SiteJungle - Hosting” (@SiteJungle), 97 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/SiteJungle.
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.