Channel
@sysadmin24x7
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
4,430subscribers
+35 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001134026408 |
|---|---|
| Type | Channel |
| Username | @sysadmin24x7 |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/sysadmin24x7 |
Hacking & security — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 10:49 | 4,430 | +1 |
| 7 Oct 2026, 10:41 | 4,429 | -6 |
| 30 Sept 2026, 17:38 | 4,435 | +9 |
| 16 Sept 2026, 11:58 | 4,426 | -1 |
| 12 Sept 2026, 19:01 | 4,427 | +2 |
| 8 Sept 2026, 16:17 | 4,425 | +5 |
| 3 Sept 2026, 07:38 | 4,420 | +1 |
| 31 Aug 2026, 04:54 | 4,419 | +6 |
| 28 Aug 2026, 11:33 | 4,413 | -3 |
| 25 Aug 2026, 19:36 | 4,416 | +4 |
| 22 Aug 2026, 16:33 | 4,412 | +4 |
| 19 Aug 2026, 11:53 | 4,408 | +4 |
| 16 Aug 2026, 18:47 | 4,404 | +4 |
| 13 Aug 2026, 02:07 | 4,400 | +2 |
| 9 Aug 2026, 17:21 | 4,398 | +2 |
| 7 Aug 2026, 00:17 | 4,396 | +1 |
| 6 Aug 2026, 04:04 | 4,395 | no change |
| 6 Aug 2026, 01:36 | 4,395 | first reading |
21 posts held, back to 30 May 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 6 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
VMSA-2026-0005.1: VMware Avi Load Balancer addresses multiple vulnerabilities (CVE-2026-47865, CVE-2026-47866, CVE-2026-47867, CVE-2026-47868, CVE-2026-47869, CVE-2026-47870, CVE-2026-47871) Advisory ID: VMSA-2026-0005.1 Advisory Severity: Critical CVSSv3 Range: 7.1 - 9.8 Synopsis: VMware Avi Load Balancer addresses multiple vulnerabilities (CVE-2026-47865, CVE-2026-47866, CVE-2026-47867, CVE-2026-47868, CVE-2026-4…
Keyv and friends compromised in active Shai-Hulud supply chain attack On August 4, 2026, attackers compromised the GitHub account of the maintainer behind keyv, a key-value storage library with roughly 127 million weekly npm downloads, and used that access to inject a credential-stealing worm across the entire package family. The same maintainer owns cacheable (29M downloads/month), flat-cache (565M downloads/month)…
Feliz SysAdminDay a tod@s Día del Administrador de Sistemas Informáticos Viernes 31 de julio de 2026
VMSA-2026-0006: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilities (CVE-2026-59309, CVE-2026-59310, CVE-2026-47876, CVE-2026-41703, CVE-2026-41709) Advisory ID: VMSA-2026-0006 Advisory Severity: Critical CVSSv3 Range: 2.7-9.8 Synopsis: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilities (CVE-2026-59309, CVE-2026-59310, CVE-2026-47876, CVE-2026-41…
Oracle Critical Patch Update Advisory - July 2026 https://www.oracle.com/security-alerts/cpujul2026.html
SonicWall SMA1000 Series Appliances Affected By Multiple Vulnerabilities Advisory ID SNWLID-2026-0008 First Published 2026-07-14 Workaround false Status Applicable CVE CVE-2026-15409, CVE-2026-15410 CWE CWE-918, CWE-94 CVSS v3 10.0 https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0008
CISA Urges SharePoint Hardening After New Exploitations Release DateJuly 14, 2026 CISA is aware of active exploitation of vulnerabilities CVE-2026-32201, CVE-2026-45659, and CVE-2026-56164, enabling cyber threat actors to gain unauthorized access to on-premises SharePoint Server instances. https://www.cisa.gov/news-events/alerts/2026/07/14/cisa-urges-sharepoint-hardening-after-new-exploitations
Microsoft - July 2026 Security Updates https://msrc.microsoft.com/update-guide/releaseNote/2026-Jul
Neutralización incorrecta de elementos especiales en FortiSandbox de Fortinet Fecha 09/07/2026 Importancia 5 - Crítica Recursos Afectados FortiSandbox 5.0: versiones desde 5.0.0 a 5.0.5; FortiSandbox 4.4: versiones desde 4.4.0 a 4.4.8; FortiSandbox Cloud 5.0: versiones desde 5.0.4 a 5.0.5; FortiSandbox PaaS 5.0: versiones desde 5.0.4 a 5.0.5. Descripción Adham El Karn, del equipo de seguridad de productos de Forti…
Bad Epoll: The bug missed by Mythos https://github.com/J-jaeyoung/bad-epoll
[Actualización 02/07/2026] Falsificación de solicitudes del lado del servidor en productos de Cisco Fecha 04/06/2026 Importancia 4 - Alta Recursos Afectados Cisco Unified CM, versión 14, y Unified CM SME, versión 15, si tienen habilitado el servicio WebDialer. Descripción Cisco ha publicado una vulnerabilidad de severidad alta que podría permitir a un atacante remoto, no autenticado, realizar ataques de falsificaci…
Múltiples vulnerabilidades en NetScaler de Citrix Fecha 03/07/2026 Importancia 4 - Alta Recursos Afectados NetScaler ADC y NetScaler Gateway 14.1 anteriores a 14.1-72.61; NetScaler ADC y NetScaler Gateway 13.1 anteriores a 13.1-63.18; FIPS de NetScaler ADC anteriores a 14.1-72.61 FIPS; Compatibilidad con FIPS y NDcPP de NetScaler ADC anteriores a la versión 13.1-37.272. Descripción Citrix ha publicado 6 vulnerabili…
Showing the 12 most recent of 21 posts we hold for @sysadmin24x7. 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.
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 3 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 13 October 2026 — this entry's latest reading, not the date you are reading this.
“SysAdmin 24x7” (@sysadmin24x7), 4,430 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/sysadmin24x7.
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.