Channel
@netblocks
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cross-platform identity · Cite this entry
50,550subscribers
-368 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001243366048 |
|---|---|
| Type | Channel |
| Username | @netblocks |
| Description | The Internet's Observatory: Tracking network disruptions and shutdowns • tools and policy for change • bridging the digital divide • https://netblocks.org |
| Created | 5 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/netblocks |
International news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
32,100 average views per post against 50,550 subscribers — an engagement rate of 63.4%. Across the 2,906 registered channels in the same cohort — 31,629–99,981 subscribers, posting mainly in English — the middle half sit between 1.91% and 12.2%, with a median of 5.54%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 12 of 12 published in the window (0 exact, 12 rounded by Telegram) |
| Views totalled | 384,670 |
| Mature posts only | 67.6% over 11 posts read at least 24h after publication |
| Subscribers | 50,550 measured 12 August 2026 |
| Cohort | b31623:eng · 2,906 channels · p10 0.437% · p25 1.91% · p50 5.54% · p75 12.2% · p90 23.6% |
| Position in cohort | 99.552th percentile · 11.5× the cohort median |
| Uncertainty | ±0.062% of the figure, from Telegram’s rounding |
| Post language | English · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:33 | 50,550 | -60 |
| 11 Aug 2026, 08:08 | 50,610 | -69 |
| 10 Aug 2026, 06:11 | 50,679 | -57 |
| 9 Aug 2026, 06:41 | 50,736 | -46 |
| 8 Aug 2026, 06:06 | 50,782 | -54 |
| 7 Aug 2026, 06:08 | 50,836 | -71 |
| 6 Aug 2026, 04:00 | 50,907 | -11 |
| 6 Aug 2026, 01:46 | 50,918 | no change |
| 5 Aug 2026, 22:00 | 50,918 | first reading |
23 posts held, back to 25 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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 23 (25 June 2026 – 11 August 2026) |
| Views total | 384,670 |
| Reactions total | 2,992 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 19:43 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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
6,165 reactions across 23 posts, in 14 distinct kinds. The most used accounts for 33.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😢 | 2,065 | 33.5% | |
| 😁 | 1,115 | 18.1% | |
| 🤬 | 920 | 14.9% | |
| 🤔 | 756 | 12.3% | |
| 😱 | 472 | 7.66% | |
| 🤯 | 281 | 4.56% | |
| ❤ | 173 | 2.81% | |
| 👍 | 102 | 1.65% | |
| 🔥 | 81 | 1.31% | |
| 🎉 | 69 | 1.12% | |
| 🤩 | 49 | 0.795% | |
| 👏 | 44 | 0.714% | |
| 👎 | 23 | 0.373% | |
| 🥰 | 15 | 0.243% |
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 23 of the 23 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 6,165reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 25 June 2026 to 11 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.
⚠️ Confirmed: Metrics show a significant decline in internet connectivity in northwest Indiana as heavy storms brings down power and telecoms lines, knocking hundreds of thousands of subscribers in the Midwest offline 🔌 #INwx
😢88🔥7😁7👍4🤬3❤2🥰1😱1
⚠️ Confirmed: Network data show disruptions to internet connectivity in parts of western #Colombia corresponding to infrastructure outages after a ~7.4 magnitude earthquake
😢131🤬12😱11😁9❤5👍4🤯3👎2
⚠️ Confirmed: Metrics show a major disruption to internet connectivity in Odesa, #Ukraine, corresponding to power outages after Russian missile and drone attacks target energy infrastructure in one of the year’s largest bombardments on the seaport city to date 📉
😢138🤬36🔥11🤩7❤6👏4🎉3👍3
⚠️ Confirmed: #Georgia has experienced the third in a series of nation-scale internet disruptions corresponding to power grid blackouts. Authorities say today's incident was triggered by tests intended to diagnose Enguri HPP systems responsible for the earlier two outages.
🤔86🤬35😁9🥰8😢8❤5🎉2👍1
⚠️ Confirmed: Analysis of network data indicates a significant decline in internet traffic in #Cuba corresponding to reports of a national power blackout. The incident comes amid continuing fuel shortages #apagón
😢122🤬37😁25👍4❤3🔥2👏1
⚠️ Confirmed: Live metrics show a gradual decline in internet connectivity in Spokane County, Washington corresponding to evacuations and emergency power shutdowns in areas affected by the Old Trails Fire, a rapidly moving wildfire 🚒
😢127😁66😱19❤8👍6🎉4🤬3🔥2
⚠️ Confirmed: Network data show that major internet provider TurkNet in #Turkey is currently experiencing a nation-scale outage, corroborating widespread user complaints; the company says engineers are working to restore service 📉
🤔486😁215🤬33😱32❤12😢9👎8👍6
⚠️ Confirmed: Metrics show a disruption to multiple social media platforms in Guinea corroborating user reports of difficulty accessing Facebook, YouTube and TikTok #Guinée
🤔63😢20🤬10❤6🔥3😁1
⚠️ Confirmed: Metrics show a significant disruption to internet connectivity in Sumy, #Ukraine corresponding to power outages after overnight Russian attacks targeting energy infrastructure 📉
😢187🤬33😁23🔥13🤩10👍5👏5👎4
⚠️Confirmed: Metrics show a disruption to internet service in #Kenya with national connectivity at 69% of ordinary levels; the incident corresponds to a widespread power outage affecting parts of the country including Nairobi 📉
🤯126😁18😢17🤬5👏3❤2🎉2🔥1
ℹ️ Note: Meta platforms including Instagram and Facebook are currently experiencing international outages; incident not related to country-level internet disruptions or filtering #InstagramDown #FacebookDown
😁214👏23❤12🤯12🎉11👍10🤩6🤔4
⚠️ Confirmed: Metrics show internet cuts corresponding to power outages in Sevastopol, occupied Crimea, intensifying amid Ukranian UAV attacks targeting energy infrastructure, with connectivity at 29% of ordinary levels as the regional Russian leadership imposes rolling blackouts
😱105🤬64❤17😁14😢9🔥7👍4🎉1
Showing the 12 most recent of 23 posts we hold for @netblocks. 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 — 1,008 of 1,151,006entries 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.
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.
Named by 19 registered channels — 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.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | NetBlocks |
|---|---|
| Description | non-governmental organization that monitors cybersecurity and the governance of the Internet |
| X / Twitter | @netblocks |
| Official site | https://netblocks.org/ |
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.
“NetBlocks” (@netblocks), 50,550 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/netblocks.
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.