Channel
@dmntrnetworksolutions
On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
905subscribers
+1 since we began measuring on 4 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001632496927 |
|---|---|
| Type | Channel |
| Username | @dmntrnetworksolutions |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/dmntrnetworksolutions |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 18:41 | 905 | +1 |
| 4 Oct 2026, 18:22 | 904 | first reading |
20 posts held, back to 19 February 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 May 2026. An engagement rate over an empty window would be a number about nothing.
186 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 44.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 83 | 44.6% | |
| ❤ | 46 | 24.7% | |
| 🔥 | 28 | 15.1% | |
| 👏 | 12 | 6.45% | |
| 🤯 | 7 | 3.76% | |
| 😱 | 5 | 2.69% | |
| 🤡 | 2 | 1.08% | |
| 🤬 | 2 | 1.08% | |
| 👻 | 1 | 0.538% |
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 18 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 186 reactions 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 19 February 2024 to 16 May 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.
🚨 Alerta temprana — CVE-2026-46333 ("ssh-keysign-pwn") en kernel Linux ⚠️ CVE-2026-46333 · CVSS 7.8 (Important) · PoC público activo · 14 de mayo de 2026 Situación La pasada semana Qualys divulgó una vulnerabilidad en el kernel Linux que permite a un usuario local sin privilegios leer ficheros propiedad de root, incluyendo las claves privadas del host SSH (/etc/ssh/ssh_host_*_key) y el contenido de /etc/shadow, sin…
👍8❤7
Actualización: Tenemos CVE asignado para que podáis realizar seguimiento de actualizaciones: https://nvd.nist.gov/vuln/detail/CVE-2026-43284
👍9❤1
🚨 Alerta temprana — Vulnerabilidad "Dirty Frag" en kernel Linux ⚠️ Sin CVE asignado · Sin parche disponible · 7 de mayo de 2026 Situación Se ha divulgado una vulnerabilidad en el kernel de Linux denominada "Dirty Frag" (también referida como "Copy Fail 2"), que permitiría escalada local de privilegios (LPE) a root. Se describe como continuación de la familia Dirty Pipe (CVE-2022-0847). A día de hoy no existe CVE as…
❤9👍8👏1
Buenos días. Hoy, otra ronda de la lotería diaria de vulnerabilidades... De lo publicado, os dejo lo que nos preocupa principalmente: -Palo Alto: Buffer overflow en User-ID Authentication Portal (CRÍTICA): Podría permitir explotación remota. Si tienes Palo Alto, ya sabes la rutina. 🔗https://www.incibe.es/incibe-cert/alerta-temprana/avisos/desbordamiento-de-bufer-en-user-id-authentication-portal-de-palo-alto -…
❤14👍1
Buenos días. Ya sabéis que estamos inmersos en esta locura preciosa de vulnerabilidades y 0-days que la IA nos está descubriendo a velocidad industrial. Antes encontrar un CVE crítico era noticia del mes; ahora es el desayuno. Vamos al lío de hoy: 🔥 OPNsense — RCE como root + bypass de lockout (PoC pública) Sí, has leído bien: ejecución remota como root y, por si fuera poco, te puedes saltar el bloqueo de cuenta. Y …
👏11❤3👍3🤡2🤬2
Estimado cliente, Le escribimos para informarle de una vulnerabilidad crítica recientemente divulgada en el kernel de Linux, conocida como Copy Fail (CVE-2026-31431), y de las medidas que hemos tomado para proteger sus sistemas. Sobre la vulnerabilidad Copy Fail es un fallo lógico en el subsistema de criptografía del kernel Linux (AF_ALG / algif_aead) presente desde 2017 y descubierta ahora. Permite a un usuario l…
👍10❤4
Photo, posted without a caption
Actualización: Cloudflare está experimentando una caída a nivel global que está afectando a múltiples servicios y clientes. Según el propio proveedor, se trata de una incidencia en su red global y ya se encuentran investigando el origen del problema. Esto puede provocar interrupciones, lentitud o errores intermitentes en los servicios que dependan de su infraestructura. Seguiremos monitorizando la situación y noti…
👍12❤2😱2
Caída de Cloudflare a nivel mundial.
👍5
Photo, posted without a caption
🔥5😱3
https://www.bleepingcomputer.com/news/microsoft/zero-click-windows-tcp-ip-rce-impacts-all-systems-with-ipv6-enabled-patch-now/
🔥7❤1👍1
Así estamos... 🙃🙃🙃
Showing the 12 most recent of 20 posts we hold for @dmntrnetworksolutions. 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.
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 1 seed channel's Telegram-generated recommendation list 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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“DMNTR Network Solutions - Alerta Temprana” (@dmntrnetworksolutions), 905 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/dmntrnetworksolutions.
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.