Channel
@arbitrumnodeupgrade
On this record: Growth · Engagement · Posts · Cite this entry
458subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001671376384 |
|---|---|
| Type | Channel |
| Username | @arbitrumnodeupgrade |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/arbitrumnodeupgrade |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 00:43 | 458 | +3 |
| 20 Aug 2026, 15:36 | 455 | +2 |
| 14 Aug 2026, 13:18 | 453 | -1 |
| 8 Aug 2026, 05:01 | 454 | no change |
| 7 Aug 2026, 20:13 | 454 | first reading |
20 posts held, back to 14 October 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 pageof 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 6 August 2026 |
|---|---|
| Posts held | 20 (14 October 2025 – 6 August 2026) |
| Views total | 87 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 05:01 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.
Hello! Nitro v3.11.3 is now available on Docker Hub: offchainlabs/nitro-node:v3.11.3-beb2108-stripped This is currently a stripped build: the Docker image is live now, but the source code is not yet published - We recommend node operators upgrade to v3.11.3 now. - The full release will follow in the next few business days, with the source code published to GitHub. If you'd rather wait for that version (For example…
Hello! During testing and monitoring, a bug was discovered on Arbitrum Sepolia relating to ArbOS 60 and its ability to charge accurate gas prices for transactions. As a result, ArbOS 61 will be deployed and activated on Arbitrum Sepolia on June 29 as early as 15:00 UTC. The first Nitro version that supports ArbOS 61 is Nitro 3.11.0, available on Dockerhub as offchainlabs/nitro-node:v3.11.0-a618155 , with the releas…
Hello! During testing and monitoring, a bug was discovered on Arbitrum Sepolia relating to ArbOS 60 and its ability to charge accurate gas prices for transactions. As a result, ArbOS 61 will be deployed and activated on Arbitrum Sepolia on June 29 as early as 15:00 UTC. The first Nitro version that supports ArbOS 61 is Nitro 3.11.0, available on Dockerhub as offchainlabs/nitro-node:v3.11.0-a618155 , with the releas…
=== ArbOS 40 Compatibility Notice: Upgrade to Nitro v3.10 + Consensus v51 === All Nitro versions and consensus releases are backward compatible with all previous ArbOS releases. However, Nitro v3.10 drops support for Consensus v40. Any chain on ArbOS 40 that upgrades validators to Nitro v3.10+ must update its WASM module root to Consensus v51.1 at the same time. We recommend that all chains upgrade to Nitro v3.10+ …
Hello! On Monday, May 18, 2026 at 17:00 UTC, ArbOS 60 is scheduled to activate on the Arbitrum Sepolia chain. Action Required Arbitrum Sepolia node operators must upgrade to Nitro `v3.10` ahead of this activation to continue syncing the chain. - Docker image: offchainlabs/nitro-node:v3.10.0-b1cf6db - Release notes: https://github.com/OffchainLabs/nitro/releases/tag/v3.10.0 Context ArbOS 60 (Elara) introduces a…
Hello! On Monday, May 18, 2026 at 17:00 UTC, ArbOS 60 is scheduled to activate on the Arbitrum Sepolia chain. Action Required Arbitrum Sepolia node operators must upgrade to Nitro `v3.10` ahead of this activation to continue syncing the chain. - Docker image: offchainlabs/nitro-node:v3.10.0-b1cf6db - Release notes: https://github.com/OffchainLabs/nitro/releases/tag/v3.10.0 Context ArbOS 60 (Elara) introduces a…
A new Arbitrum Nitro version 3.9.9 is now available on Docker Hub with the following tag: offchainlabs/nitro-node:v3.9.9-6b0af88-stripped This is an important release containing stability improvements and security fixes, and we recommend teams adopt it as soon as possible. The source code will be published in the coming days. Following that, a non-stripped version of the Nitro node software will be made available u…
Hello! Arbitrum nodes can now run in archive mode using PathDB! More information can be found in our docs! https://docs.arbitrum.io/run-arbitrum-node/more-types/run-archive-node#archive-path-node-configuration-details
Hello! As a follow up to Monday’s (March 23 2026) Arbitrum Sepolia network outage and out of an abundance of caution, we are asking all node operators to upgrade all of their nodes to Nitro 3.9.8 at their earliest convenience. This release is available as a Docker Image on Docker Hub at offchainlabs/nitro-node:v3.9.8-4624977. This recommendation applies to node operators for all Arbitrum chains. Thank you for your…
Hello! Arbitrum Sepolia block production has been restored. Developers: transactions and deployments on the Arbitrum Sepolia network should now be working as usual again. Node operators and infrastructure providers: as mentioned before, a new Nitro release will be published later - all node operators will be asked to upgrade to that version when it is ready. Instructions will be included in a later update. Please…
Hello! Arbitrum Sepolia is currently experiencing a partial outage. As a precaution, block production on Arbitrum Sepolia has been temporarily halted while the team investigates. We are investigating a potential root cause related to Nitro software causing a block divergence and are actively working on an infrastructure update to restore block production. No user funds are at risk. Developer guidance - Expect tr…
Hello! Following the recent Ethereum BPO change, we observed a brief window where Arb1 batch posting intermittently stalled during periods of elevated blob gas pricing, leading to temporary backlogs; this issue has been fully resolved, the backlog was cleared overnight, and batch posting is operating normally again. The root cause was a configuration mismatch in older Nitro versions affecting blob pricing calculatio…
Showing the 12 most recent of 20 posts we hold for @arbitrumnodeupgrade. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Arbitrum Node Upgrade Announcement” (@arbitrumnodeupgrade), 458 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/arbitrumnodeupgrade.
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.