Channel
@cloudandcybersecurity
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
21,884subscribers
-34 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001371647277 |
|---|---|
| Type | Channel |
| Username | @cloudandcybersecurity |
| Description | Cloud Computing and Cybersecurity career advice, AWS and Cybersecurity quizzes, tips and useful resources to help you succeed in the field. |
| Created | Between 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/cloudandcybersecurity |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 08:02 | 21,884 | -1 |
| 11 Aug 2026, 07:09 | 21,885 | -7 |
| 10 Aug 2026, 08:35 | 21,892 | -17 |
| 9 Aug 2026, 05:02 | 21,909 | -8 |
| 8 Aug 2026, 02:46 | 21,917 | -1 |
| 7 Aug 2026, 07:45 | 21,918 | no change |
| 7 Aug 2026, 07:36 | 21,918 | first reading |
20 posts held, back to 20 June 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 17 pagesof Telegram’s post history, 20 posts per page.
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 7 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 20 (20 June 2026 – 1 August 2026) |
| Views total | 15,724 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 23:05 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.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
39 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 87.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 34 | 87.2% | |
| 😁 | 2 | 5.13% | |
| 👏 | 1 | 2.56% | |
| 👨💻 | 1 | 2.56% | |
| 🔥 | 1 | 2.56% |
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 14 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 39reactions 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 20 June 2026 to 1 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.
Joining me live today? Every Saturday from 11 AM to 12 PM EST I host one hour of open office hours for students in my Skool community at www.yescertified.com. Bring your questions, career related, technical, certification prep, job search, whatever you are working through right now. I show up personally every week and answer everything live. This is not a recorded session. This is direct, real time access to a CIS…
👨💻1
Photo, posted without a caption
Important Announcement! On August 14th, 2026 the price increases from $15 to $50 a month. That is two weeks away. Anyone enrolled before that date locks in $15 a month forever, no matter how high the price goes after that. Here is what you are getting right now while the course is actively being built. While you are learning, you have something most paid courses never offer. One hour of live access to me every Sa…
❤1
Photo, posted without a caption
New video just dropped in the Cybersecurity course on Skool. This video was recorded in July 2026 (to be precise, today). Everything you see is current, the interface, the steps, the configuration. No outdated screenshots, no "this might look slightly different on your version." Just a clean, up to date walkthrough that actually works. This covers how to set up Nessus, one of the most widely used vulnerability scan…
❤3
Photo, posted without a caption
Yescertified.com Newsletter - Cloud Security Architecture Decisions You Must Avoid (No. 1) This one is the start of a new series I am calling "Cloud Security Architecture Decisions You Must Avoid," and I am kicking it off with one of the most common mistakes I see in real AWS environments. Most teams assume that putting workloads in separate VPCs inside the same AWS account is enough isolation. It is not, and I hav…
New video just dropped in the Cybersecurity course on Skool. This one covers SSH and iptables, specifically how to configure firewall rules to control SSH access. If you have ever wondered how traffic is actually allowed or blocked on a Linux system before it even reaches the application, this is the video that makes it click. 26 minutes of hands-on, practical content. No fluff. I am currently recording and upload…
❤1
Two new videos uploaded to the Cybersecurity course: - Resolve OpenVAS Findings - Authenticated scan with OpenVAS
❤2
New video just dropped in the Cybersecurity course. I built a custom OpenVAS analyzer tool that transforms raw vulnerability scan output into a clean, prioritized findings dashboard, and this video walks through exactly how it works. I also made a public version you can share with anyone interested in getting into cybersecurity. It gives a real look at the kind of hands-on work we do inside the course. Watch it her…
❤3😁2
Today's newsletter is about a Cloud Security tool you should definitely make sure you know before any Cloud Security interviews. Read it at the link below, https://yescertified.beehiiv.com/p/the-cloud-and-ai-security-newsletter-5-the-cloud-security-tool-your-resume-is-missing-part-4 If you haven't already, sign up for my newsletter here, https://yescertified.beehiiv.com, it's free. I'm on Skool: https://www.skool.c…
❤1
In the upcoming video, I'll show you how I used a custom tool I built to make it easy to analyze the results of the vulnerability scans
❤1
Showing the 12 most recent of 20 posts we hold for @cloudandcybersecurity. 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 — 845,924 of 1,160,990entries 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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Cloud and Cybersecurity” (@cloudandcybersecurity), 21,884 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/cloudandcybersecurity.
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.