The incident is resolved
👍1

Channel
@dune_updates
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,114subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001980783391 |
|---|---|
| Type | Channel |
| Username | @dune_updates |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 2 times, most recently 17 November 2026 |
| On Telegram | t.me/dune_updates |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 23:19 | 1,114 | +2 |
| 7 Nov 2026, 17:17 | 1,112 | -1 |
| 29 Oct 2026, 04:38 | 1,113 | -4 |
| 25 Oct 2026, 22:49 | 1,117 | -5 |
| 22 Oct 2026, 12:06 | 1,122 | +2 |
| 19 Oct 2026, 06:46 | 1,120 | -2 |
| 7 Oct 2026, 10:38 | 1,122 | -4 |
| 30 Sept 2026, 12:57 | 1,126 | -10 |
| 19 Sept 2026, 17:21 | 1,136 | -8 |
| 11 Sept 2026, 21:56 | 1,144 | +2 |
| 7 Sept 2026, 06:41 | 1,142 | -2 |
| 2 Sept 2026, 11:28 | 1,144 | +2 |
| 27 Aug 2026, 17:24 | 1,142 | +1 |
| 25 Aug 2026, 00:05 | 1,141 | -3 |
| 21 Aug 2026, 05:47 | 1,144 | -4 |
| 17 Aug 2026, 23:25 | 1,148 | -2 |
| 14 Aug 2026, 13:27 | 1,150 | -1 |
| 11 Aug 2026, 09:23 | 1,151 | -1 |
| 7 Aug 2026, 10:32 | 1,152 | no change |
| 7 Aug 2026, 10:29 | 1,152 | first reading |
20 posts held, back to 1 December 2025 — 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
14 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 42.9% | |
| 👍 | 5 | 35.7% | |
| 🔥 | 2 | 14.3% | |
| 🤯 | 1 | 7.14% |
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 9 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 14 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 1 December 2025 to 4 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.
The incident is resolved
👍1
We are currently facing issues with our query execution backend. https://status.dune.com/ Our team is remediating
We will be running maintenance operations on Wednesday May 27th between 10am CEST and 10:30am CEST. The app will be unavailable for a few minutes, during which you will be unable to access dashboards, use the API, or run queries.
❤1👍1
This incident is now fully resolved
❤4🔥2
We are facing issues with our data pipelines : The following datasets are stale since ~2am UTC today. - tokens.transfers - tokens_solana.transfers - dex.trades - dex_solana.trades - nft.trades Follow the incident live here : https://status.dune.com/incident/877388
This has been restored and tables have been resolved
We're currently investigating an issue affecting a large number of curated data models, which have not received updates since 17:00 UTC. This includes: • dex.trades • tokens.transfers • lending.supply • nft.transfers You may see stale data or query failures referencing these tables while we work on a resolution. Our engineering team has identified the cause and is working on a fix. Live status: https://status.dune.…
Heads up that we're currently working through a data freshness issue affecting both dex.trades and tokens.transfers. Both tables have been stale since ~03:00 UTC this morning. The underlying cause has been mitigated and the tables are backfilling now. Current estimates: dex.trades should be caught up within ~1 hour, and tokens.transfers within ~2 hours. I'll follow up once both are fully current.
👍2
this has been resolved
Heads up - We’re going to pause Solana decoding to resolve some fixes. Solana decoding data will be stale until we resume it.
🤯1
this has now been resolved
We are currently mitigating an issue where historical data for Solana DEX trades is temporarily unavailable. Queries and dashboards relying on this data are currently only returning results from the last few days rather than the full historical range. Our engineering team has identified the root cause and a fix is already in progress. Historical data is being backfilled and we expect full resolution within approximat…
Showing the 12 most recent of 20 posts we hold for @dune_updates. 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Dune Updates” (@dune_updates), 1,114 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/dune_updates.
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.