1790257576714.pdf

Channel
F5 | PALOALTO | CHECKPOINT | SOPHOS | FORTIGATE | Zscaler | Cisco
@CyberSecFirewalls
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
2,203subscribers
+102 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001477896654 |
|---|---|
| Type | Channel |
| Username | @CyberSecFirewalls |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 8 November 2026 |
| On Telegram | t.me/CyberSecFirewalls |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 the other topics.
Previous handles
@CyberSecFirewalls was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 11 August 2026 – 11 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 14:10 | 2,203 | +2 |
| 2 Nov 2026, 05:58 | 2,201 | -2 |
| 30 Oct 2026, 13:05 | 2,203 | +4 |
| 27 Oct 2026, 06:46 | 2,199 | +4 |
| 24 Oct 2026, 07:30 | 2,195 | -1 |
| 20 Oct 2026, 21:27 | 2,196 | +2 |
| 14 Oct 2026, 10:06 | 2,194 | +3 |
| 10 Oct 2026, 18:20 | 2,191 | +6 |
| 4 Oct 2026, 17:55 | 2,185 | +8 |
| 27 Sept 2026, 11:22 | 2,177 | +16 |
| 12 Sept 2026, 00:39 | 2,161 | +1 |
| 7 Sept 2026, 14:55 | 2,160 | +7 |
| 2 Sept 2026, 12:35 | 2,153 | +4 |
| 30 Aug 2026, 05:28 | 2,149 | +5 |
| 27 Aug 2026, 02:12 | 2,144 | +11 |
| 24 Aug 2026, 10:22 | 2,133 | +4 |
| 20 Aug 2026, 13:07 | 2,129 | +3 |
| 17 Aug 2026, 18:06 | 2,126 | +10 |
| 15 Aug 2026, 00:02 | 2,116 | +14 |
| 11 Aug 2026, 23:17 | 2,102 | first reading |
Engagement
33 posts held, back to 30 January 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 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 33 posts for this entry, the most recent from 24 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 10m 05s
- Average length
- 5m 03s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
< FortiGate Firewall Lab - Hands-On Guide I Volume 1 I'm happy to share that I've completed Volume 1 of my FortiGate Firewall Lab Guide, developed as a practical, hands-on reference for network and security engineers. The goal of this guide is not just to demonstrate confiquratior commands, but to focus on the complete workflow: Configure - Verify -> Troubleshoot --> Identify Root Cause --> Fix -> Validate F Topics c…
Hi
Posted without readable text
Channel name was changed to «F5 | PALOALTO | CHECKPOINT | SOPHOS | FORTIGATE | Zscaler | Cisco»
🚨 Network running slow, but all dashboards say "Green"? Stop guessing and start troubleshooting at the packet level! 🕵️♂️🔍 I just dropped a new video walkthrough for my course: Wireshark A-to-Z: Enterprise Network Troubleshooting. Most tutorials just give you a tour of the UI. This course skips the fluff and hands you 30+ REAL PCAP lab files to solve enterprise-grade issues yourself. Watch the video above ☝️ to see …
Hey everyone 👋 Sharing something useful — I just published my Wireshark course on Udemy and wanted to give this group early access with a discount coupon 🎓 📦 What's inside: ✅ 39 hands-on labs with real PCAP files ✅ 9+ hours of content ✅ TCP, DNS, TLS, HTTP, FTP analysis ✅ Security attacks — ARP poisoning, DNS tunneling, C2 beaconing ✅ IPSec VPN troubleshooting ✅ Wireshark for forensics + AI integration ✅ Capstone r…
🦠 Ransomware Attack & Prevention Understand ransomware attacks, how they work, their impact, and strategies to prevent and defend against them. 👉 https://www.udemy.com/course/ransomware-attack-prevention/
Palo Alto Firewall & Panorama Hardenin gLearn how to harden Palo Alto Firewall and Panorama configurations and improve your network security posture .👉 http://udemy.com/course/palo-alto-and-panorama-hardening-the-configuration/
🔎 Web Application Penetration Testing – A to Z 👉 https://www.udemy.com/course/web-app-penetration-testing-a-to-z/?couponCode=DD6751564E32E9C53875
🦠 Ransomware Attack & Prevention 👉 https://www.udemy.com/course/ransomware-attack-prevention/?couponCode=7E336089E39DD1BA8074
🛡️ Web Application Penetration Testing 👉 https://www.udemy.com/course/web-app-penetration-testing/?couponCode=514D1277127987FB173D
Showing the 12 most recent of 33 posts we hold for @CyberSecFirewalls. 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
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.
Appears in Telegram’s recommendations for other channels
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.
@CCNA_CCNP_HUAWEI · 19,264
Telegram ranks this channel #15 of 62 here — alongside 61 others — read 2 October 2026
@pythonnotes1 · 75,076
Telegram ranks this channel #31 of 69 here — alongside 68 others — read 19 August 2026
@Hariskumar0 · 19,990
Telegram ranks this channel #41 of 79 here — alongside 78 others — read 27 September 2026
@learningnets · 31,085
Telegram ranks this channel #41 of 56 here — alongside 55 others — read 7 September 2026
@Jobs_2COMS · 28,820
Telegram ranks this channel #47 of 66 here — alongside 65 others — read 8 September 2026
@MPSCEnglish · 53,362
Telegram ranks this channel #58 of 76 here — alongside 75 others — read 23 August 2026
@rojgar_UPSC_Lucent_Sirk_GK_khan · 149,945
Telegram ranks this channel #59 of 63 here — alongside 62 others — read 12 August 2026
@All_Exams_PYQs_SSC_GD_CGL_GK · 182,407
Telegram ranks this channel #60 of 61 here — alongside 60 others — read 11 August 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“F5 | PALOALTO | CHECKPOINT | SOPHOS | FORTIGATE | Zscaler | Cisco” (@CyberSecFirewalls), 2,203 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/CyberSecFirewalls.
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.