io.net engagement report
@ionet - 426K followers on X
Measured over 35 original posts from a 30-day window, last computed on September 24, 2026.
Engagement
A typical post picks up 165 interactions against 426K followers, an engagement rate of 0.038%. Measured over 35 original posts, its engagement rate beats 55% of 20,444 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 14K times each, and 1.19% of those impressions turn into an interaction. That is about 3.24% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.2 posts a day over the last 30 days, with activity on almost every day in the window. Most posts go out around 08:00 UTC, and Thursday is the busiest day of the week. Of the 35 posts sampled, 89% carry an image or video, 54% are part of a thread and 54% link out. The account's strongest tracked post pulled 941 interactions, about 5.7x its own typical post.
Measured over 35 original posts from a 30-day window, last computed on September 24, 2026.
Compared with accounts its own size
io.net's engagement rate beats 55% of the tracked X accounts closest to it in follower count (20,444 accounts, accounts of similar size (decile 10 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.
On engagement per impression rather than per follower it beats 52% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.
Where this sits in the catalog
At 0.038%, io.net sits above the 25th percentile of the 205,048 accounts in this comparison. That places it in the below the median band, which runs 0.024% to 0.143%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.004% |
| 25th percentile | 0.024% |
| 50th percentile | 0.143% |
| 75th percentile | 0.678% |
| 90th percentile | 2.55% |
| 99th percentile | 82.4% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 08:00 UTC, and Thursday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 89K |
| 01:00 UTC | -2% | 90K |
| 02:00 UTC | -3% | 88K |
| 03:00 UTC | -4% | 94K |
| 04:00 UTC | -5% | 76K |
| 05:00 UTC | -4% | 75K |
| 06:00 UTC | -5% | 86K |
| 07:00 UTC | -5% | 93K |
| 08:00 UTC | -4% | 108K |
| 09:00 UTC | -4% | 124K |
| 10:00 UTC | -3% | 129K |
| 11:00 UTC | -3% | 141K |
| 12:00 UTC | -3% | 154K |
| 13:00 UTC | -3% | 167K |
| 14:00 UTC | -4% | 173K |
| 15:00 UTC | -2% | 176K |
| 16:00 UTC | -3% | 171K |
| 17:00 UTC | -3% | 159K |
| 18:00 UTC | -2% | 149K |
| 19:00 UTC | -2% | 141K |
| 20:00 UTC | -1% | 131K |
| 21:00 UTC | 0% | 116K |
| 22:00 UTC | -2% | 100K |
| 23:00 UTC | -1% | 90K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 393K |
| Monday | +1% | 483K |
| Tuesday | -2% | 520K |
| Wednesday | -3% | 472K |
| Thursday | -2% | 430K |
| Friday | -3% | 447K |
| Saturday | +2% | 393K |
Formats this account uses
Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.
| Format | This account | Catalog effect | 95% interval | Accounts behind it |
|---|---|---|---|---|
| Image or video | 89% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 54% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | +15% | +14% to +16% | 32K |
- 89% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
- 54% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
- Its average post runs 385 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.
These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.
Best tweets
- Jun 11, 20265.7x their median
The future of AI compute doesn't run on hype. It runs on real utility, real burns, and a network that gets stronger every time it's used. The Incentive Dynamic Engine (IDE) is now live! https://t.co/ggOg5dBdZw https://t.co/Ylmj9jH0d0
- Aug 24, 20261.6x their median
27 million dollars paid out. Not raised or projected. Paid. That's real money flowing to real GPU providers, for real compute delivered on https://t.co/WLXlHkv6f1. This is what the future of AI compute looks like. https://t.co/tcCnNRP29P
- Sep 10, 20261.5x their median
2 million burned. Gone for good. Because of real utility and real value flowing through the network. Usage creates value. Value reduces supply. The flywheel is turning. Powered by the IDE. https://t.co/twM9VgWVLQ
- Aug 29, 2026
Some things do exactly what they say. Render Network is great at what it was built for: rendering. But AI workloads ask for something else. Persistent inference. Multi-node training. Clusters that scale in seconds. That’s orchestration, not just GPU access. And that's what https://t.co/ZuybGWvjv9 was built for that from day one. https://t.co/YQC5wpjIu3
- Sep 19, 2026
$2.7 trillion. That’s how much the world will spend on AI in 2026. And more than half will go to infrastructure. This is the biggest infrastructure project humanity has ever undertaken. But who controls that infrastructure will decide who gets to build. AI needs more compute. And more people need access to it. That's what @ionet is here for. https://t.co/mExHxIjI42
- Aug 31, 2026
33 million+ compute hours served on https://t.co/ZuybGWvjv9. A live network, doing the work hyperscalers and neoclouds charge a premium for. Every one of those hours is proof. You don't need expensive, gatekept infrastructure to run serious AI workloads. Decentralized compute isn't a narrative. It's the future of AI infrastructure.
- Sep 11, 2026
2 million new GPUs. That's the deal @awscloud and @nvidia announced this week. It's also the problem. That compute will get reserved before it's even built by whoever can write the biggest check. And growing projects, indie builders, small labs, and researchers will still have to wait in line. GPU capacity exists today, sitting idle, that doesn't require billions to build or buy. @ionet is unlocking it.
- Aug 6, 2026
Google Cloud Platform H100: $11.06/hr. https://t.co/ZuybGWvjv9 H100: $1.49–2.20/hr. 87% extra for a logo, not performance. Same NVIDIA silicon. Same CUDA stack. Same PyTorch. The difference is a quota form, a 3-7 day wait, and a hyperscaler margin. We skipped all three. Deploy in <2 minutes. No queue.
- Sep 7, 2026
8 billion tokens. That's what ran through @ionet models on @OpenRouter. In a single day. This isn't a benchmark or a demo. It's real inference and real demand running on affordable and accessible infrastructure. This is what AI for the many, not the few, looks like. https://t.co/lNgdL62qDM
- Sep 20, 2026
96 GPUs in under 24 hours with zero waiting. That's what it took for @wonderaai to go from compute-constrained to shipping. 64 H100s and 32 H200s rapidly provisioned on @ionet. Not queued for months on a waitlist. The results: - 200,000 users in 4 months, across 171 countries - 50% month-over-month growth - Launched 3 months ahead of schedule This is what happens when your compute keeps up with how fast you can build. https://t.co/N1qL3tXv2j
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Buy or sell Twitter (X) accounts - escrow-protected
PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 165 interactions against 426K followers, an engagement rate of 0.038%. Measured over 35 original posts, its engagement rate beats 55% of 20,444 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 14K times each, and 1.19% of those impressions turn into an interaction. That is about 3.24% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.2 posts a day over the last 30 days, with activity on almost every day in the window. Most posts go out around 08:00 UTC, and Thursday is the busiest day of the week. Of the 35 posts sampled, 89% carry an image or video, 54% are part of a thread and 54% link out. The account's strongest tracked post pulled 941 interactions, about 5.7x its own typical post.
- What is io.net's engagement rate on X?
- io.net (@ionet) has an engagement rate of 0.038%, based on the median interactions across 35 original posts from the last 30 days against 426,355 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.038%, io.net sits above the 25th percentile of the 205,048 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @ionet have real engagement?
- Its engagement rate beats 55% of the tracked X accounts closest to it in follower count (20,444 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
- When does @ionet post?
- Most posts go out around 08:00 UTC, and Thursday is its busiest day, at roughly 2.17 posts per day across the measured window.