The first EmberNode leaderboard is already taking shape, and it is moving faster than many people expected.
In the first week of May, the average active EmberNode moved 180GB of data. The leading EmberNode moved 575.64GB. That is more than 70% of the 800GB monthly planning benchmark in just seven days.
The top 10 all moved more than 418GB. The top 20 all moved more than 392GB.
The average matters. It gives useful context. But the leaderboard tells a more interesting story. Some EmberNodes are still ramping. Others are already moving serious traffic.
A different kind of AirNode
EmberNodes operate differently to Spark AirNodes. They play a different role in the World Mobile network, and that difference matters.
Spark AirNodes connect users closer to the edge of the network. EmberNodes sit further upstream, helping distribute traffic from ISP backhaul into downstream network hardware and services. That can include Spark AirNodes, partner networks, devices, and other endpoint hardware.
So a Spark AirNode and an EmberNode should not be judged as if they perform the same job. One sits closer to the user. The other supports the distribution layer that helps traffic move through the network.
Different layer. Different dynamics. Different performance profile.
The first-week May leaderboard
The table below shows selected top EmberNode performers for the first week of May, alongside the average across all active EmberNodes.
The 800GB benchmark is monthly
The 800GB EmberNode planning benchmark is a monthly benchmark. That is important.
It was built from months of planning, measurement, and observed performance across an operating AirNode environment in Pakistan. It was not guessed. It was not created from a single week of EmberNode activity. It was used as a planning marker for what this layer is designed to support as usage develops.
Now compare that monthly benchmark with the first-week May leaderboard. The leading EmberNode moved 575.64GB in seven days, already over 70% of the monthly planning benchmark.
At the same pace, that top node would track toward roughly 2.47TB over a 30-day month.
That is not a promise of future performance. It is a simple run-rate view based on the first seven days of May. But it does show why the leaderboard matters.
When an EmberNode starts moving, it can move quickly.
The average tells one story. The leaderboard tells another.
The average active EmberNode moved 180GB in the first week of May. That number is useful, but averages can flatten the story. They blend high performers, developing nodes, lower-traffic locations, and nodes still building downstream activity into one figure.
The leaderboard gives a sharper view.
The leading EmberNode moved more than three times the active-node average during the same period. The top 20 all moved more than 392GB, putting every one of them close to half of the 800GB monthly planning benchmark in only seven days.
That does not mean every EmberNode will perform like the top 20. It does mean the first leaderboard is already showing range.
And in a usage-driven network, range is the point.
What separates top performers?
The top EmberNodes are not all moving at the same pace because the conditions around them are not identical.
Performance can be shaped by:
- Throughput
- Local demand
- Uptime
- Downstream connectivity
- Connected endpoint hardware
- Network density
- Services using the distribution layer
- The amount of traffic moving through the local network path
This is why one screenshot rarely tells the full story.
A lower-performing EmberNode may still be early in its lifecycle. A stronger-performing EmberNode may already sit in a better traffic path, with stronger demand or more downstream activity around it.
That is what makes the leaderboard worth watching.
It shows the network becoming more legible.
Why the first leaderboard matters
World Mobile has always been built on a simple idea: the people who help power the network should share in the value they help create.
AirNodes turn that idea into infrastructure. EmberNodes bring it into the distribution layer.
Every gigabyte moved through an EmberNode is part of a wider path: ISP backhaul, downstream connectivity, endpoint hardware, services, and users connecting through the network.
That is why the first-week May numbers matter. They are not just a table. They are an early view of a competitive performance layer forming inside the network.
Operators can now look at the spread. They can compare average performance with top performers. They can see how quickly a node can move toward the monthly benchmark when conditions align. And they can watch the leaderboard develop over time.
This is only the beginning
The first-week May data gives the community a clearer view of EmberNode performance.
Average active EmberNode: 180GB.
Top performer: 575.64GB.
Top 10: all above 418GB.
Top 20: all above 392GB.
Monthly planning benchmark: 800GB.
The leading EmberNode has already covered more than 70% of that monthly benchmark in one week.
That is the signal.
As always, individual outcomes vary. Forecasts are not guarantees. Performance depends on usage, uptime, demand, downstream connectivity, and wider network conditions.
But the leaderboard is forming. The top performers are separating from the pack. And the distribution layer of the World Mobile network is beginning to show what it can do.
The next EmberNode drop opens Wednesday 13th May at 4pm UTC.
.png)
