Event Notes - August 28, 2026

T-Mobile Offload via Ameriband Is Ending

A Helium Discord community call on the August 31 end of the current T-Mobile offload integration through Ameriband, its expected impact, deployer changes, and possible paths forward.

SourceDiscord community call recording
Duration23m 50s
ParticipantsHelium team and community

Executive Summary

  • The T-Mobile offload path through Ameriband ended August 31: The affected relationship was identified within the Helium community as T-Mobile traffic routed through Ameriband. Mario Di Dio did not name either company in the official post or the call, citing contractual restrictions. All T-Mobile selections were removed network-wide on August 31; as of September 1, no hotspots pass T-Mobile offload traffic.
  • The 30% estimate was about daily active users, not traffic bytes: Mario estimated that daily active users would fall by about 30% and described the change as almost one million people disconnecting. Network-wide records show that T-Mobile represented nearly half of Mobile traffic before the disconnect, including 47.29% of rewardable traffic bytes.
  • Greenfield and Brownfield deployments required different operational changes: The call said Greenfield Hotspots would receive a configuration update disabling the affected carrier's Passpoint profile, while Brownfield deployers would remove it from their controller configurations. Backend AAA controls and a NAS ID denylist would also block the traffic.
  • The call did not present this as a network-quality failure: Mario described tension between Nova's model and the third-party integrator's competing business model, combined with the carrier becoming less receptive to Wi-Fi from non-enterprise accounts. He characterized the decision as partly commercial and organizational, not only technical, and said Helium's deployment quality was not the reason.
  • Other carrier relationships continue: Mario said AT&T, Telefonica/Movistar, other MVNOs, and the rest of Helium's carrier roster were not affected. He left open the possibility that the affected carrier could return through a direct, venue-specific, or otherwise different arrangement, but no replacement T-Mobile integration has been publicly announced.
  • HIP 150 materially increased the data-transfer reward pool: Nova redirected its Service Provider rewards to data deployers, moving the baseline Mobile data allocation from 70% to 94%. The HIP also raised the target minimum from 50% to 80% of the payer rate; at $0.10/GB, that target is $0.08 per rewardable GB. Location multipliers still require separate commercial approval.

August 31 Outcome

The planned disconnect was completed on August 31. All T-Mobile selections were removed from the network; as of September 1, no hotspots pass T-Mobile offload traffic.

T-Mobile offload
Stopped
No hotspot traffic after the network-wide selection removal
Earnings per rewardable GB
25.57¢
August 31, 2026 UTC epoch

Why the 25.57¢ Rate Increased

The August 31 rate cannot be attributed to the T-Mobile removal alone. Three separate changes pushed USD earnings per rewardable GB upward:

  1. HNT appreciated before the disconnect. CoinGecko's UTC daily close rose from $0.1909 on August 24 to $0.7663 on August 30, roughly quadrupling before T-Mobile traffic was removed. The network uses its own HNT oracle price for rewards, but the market move explains why USD earnings per GB had already started climbing.
  2. HIP 150 enlarged the data-transfer pool. Nova redirected its Service Provider rewards to data deployers, increasing the baseline Mobile data allocation from 70% to 94% of the Mobile subDAO slice, or about 34% relative to the previous pool.
  3. Rewardable traffic then fell. T-Mobile represented 47.29% of rewardable bytes in the preceding 30-day measurement. Once that traffic stopped, the enlarged HNT pool was distributed across substantially fewer rewardable bytes.

Three parameters move the rate: More HNT allocated to data deployers raises it. A higher epoch HNT/USD oracle price raises its dollar value. More rewardable traffic spreads the pool across more data and lowers the per-GB rate, while less traffic raises it.

The HNT-allocation parameter is not fixed. It starts with baseline Mobile emissions, includes HIP 150's redirected Service Provider rewards, and can receive a backstop top-up when needed to reach the target minimum. If earnings would exceed the cap, the excess is redirected away from data deployers.

HNT price, reward-pool size, and rewardable traffic volume all changed around the transition. The 25.57¢ result reflects their combined effect, not a clean measurement of any one factor.

This is the first post-removal observation, not a guaranteed or stable rate. Higher earnings per GB also do not necessarily mean higher total earnings: deployers that lost significant T-Mobile traffic may earn less overall even while the remaining rewardable traffic pays more per GB.

For a measured day-by-day breakdown, read Why did Helium Mobile earnings per GB jump to 25.57 cents?

What Happened

Mario opened the substantive part of the call by referring to the metrics update published earlier that day. He said one relationship in Helium's carrier roster would end on Monday, August 31, because the third-party integrator used to bring that carrier onto the network was ending the arrangement.

The official announcement, blog post, and call describe a U.S. carrier and third-party integrator without naming them. Within the Helium community, the affected integration has been identified as T-Mobile offload routed through Ameriband. The distinction matters: the currently mediated offload path is ending, but neither Mario nor the official post announced that every possible future relationship with T-Mobile is over.

Immediate Network and Deployer Changes

Mario said Greenfield Hotspots would receive a configuration update that turns off the affected carrier's Passpoint profile. For Brownfield networks, Helium's sales team would contact partners with instructions to remove the carrier configuration from their controllers.

Joey Padden added that the carrier would also be blocked through the AAA layer. Brownfield operators were still being asked to remove the profile locally because leaving a profile visible while authentication fails could produce connection attempts and a poor subscriber experience. The team said avoiding that outcome matters if Helium later pursues a direct relationship with the same operator.

The largest headline impact is activity. Mario estimated an approximately 30% reduction in daily active users and later referred to almost one million people disconnecting. While discussing deployer economics, he also used the phrase "30% less traffic," but the earlier and more specific estimate was framed as a change in daily active users. User counts and transferred bytes are different measurements and should not be treated as interchangeable.

HeliumGeek's network-wide verified data-transfer records give a separate view of the byte-level exposure before the disconnect:

This pre-disconnection split showed how much rewardable traffic was exposed to the change. After the August 31 selection removal, T-Mobile offload traffic fell to zero. Longer-run changes in total network volume and deployer earnings require additional complete UTC epochs.

Why the Integration Ended

Mario separated the cause into two related issues. First, he described a direct business-model conflict between Nova and the third-party aggregator carrying the traffic. In his account, Helium's growth increasingly overlaps with the aggregator's own commercial model, creating friction over how far Helium should expand.

Second, he said the carrier itself had become less trusting of Wi-Fi, particularly Wi-Fi coming from non-enterprise accounts. He contrasted that stance with AT&T and Telefonica/Movistar, which he said approach Helium's quality-controlled Wi-Fi model differently. He described the decision as being as much about internal incentives and organizational politics as technology.

Mario explicitly argued that the change was not caused by the quality of Helium deployments. That is Nova's position, not an independently disclosed statement from the carrier or integrator. Neither Ameriband nor T-Mobile has publicly explained the decision in the source material available for this event.

Short-, Medium-, and Long-Term View

In the short term, the focus is removing the carrier configuration cleanly, measuring the impact, and supporting deployers whose traffic falls. Mario linked that support directly to HIP 150 and its changes to the deployer earnings floor and location multipliers.

For the medium term, Mario said the relationship could return in a different form. He mentioned conditions tied to deployment type, direct engagement, or an approach focused on specific venues. He also warned against assuming a quick return: it could take months or longer, and no new structure was announced.

For the long term, Mario said his Wi-Fi convergence thesis had not changed. He argued that cellular economics will eventually force carriers to use Wi-Fi as a peer access layer. As one industry signal, he pointed to Vodafone Spain returning 3.5 GHz spectrum rather than carrying the cost of deploying and holding it.

HIP 150 and Deployer Economics

At the time of the call, HIP 150 voting was open and scheduled to close August 31 at 18:11 UTC. Marc Nijdam said the blockchain and oracle changes were ready, with final oracle testing underway, and that implementation could follow the vote.

The speakers stressed that passage would not automatically grant reward multipliers. The proposal creates the mechanism, but an individual multiplier still depends on an agreement involving the deployer, Nova's business-development team, and carrier economics. Existing Brownfield deployers and Helium Plus partners would not need to join a separate program, but they would need to be in Helium Plus to be eligible for a multiplier.

The immediate broad change would be the higher target minimum. With the current payer rate at $0.10/GB, the proposal raises the deployer target from 50% to 80%, or from $0.05 to $0.08 per rewardable GB. That improves the rate applied to traffic that remains, but it does not replace traffic that disappears when an integration ends.

Field Evidence and a Possible Future Relationship

Mario asked deployers to report locations where disabling the integration creates a measurable decline in subscriber experience. He directed reports to business@helium.com or mario@helium.com, with business locations and, where possible, direct feedback from venue owners that Nova can use in future carrier discussions.

He said quality metrics and network data had already been used to support Nova's case, but argued that bottom-up evidence from places where Helium filled real coverage gaps could make the impact harder for the carrier to ignore. The request also included an important qualification: some deployments are more useful than others, so the team is looking for specific evidence rather than general dissatisfaction.

Other Carrier and Product Updates

Asked about Verizon, Mario said the carrier had started exploring Wi-Fi offload in specific verticals and was taking a cautious approach. He expected any Verizon relationship to move even more slowly than some of Helium's existing carrier discussions.

Mario also previewed product announcements and field validation expected the following week. He said those products already had a customer pipeline and were intended to advance Helium's network-offload thesis. Because the details were not yet public during this call, whether those products convert into announced customers and material traffic remained an open follow-up.

On Helium Plus processing, the team said carrier submission lists are normally sent weekly. Some July and August lists took longer because of carrier-side vacations and staff turnover, but new personnel were being trained and the expected submission cycle was returning to about one week.

Numbers and Claims to Track

  • Call duration: 23m 50s.
  • All T-Mobile selections were removed network-wide on August 31, 2026; as of September 1, no hotspots pass T-Mobile offload traffic.
  • Estimated daily-active-user decline: about 30%. This was a user-count estimate, not a measured traffic-byte share.
  • Mario described the affected audience as almost one million people.
  • Earnings reached 25.57 cents per rewardable GB for the August 31 UTC epoch, the first post-removal observation.
  • CoinGecko's UTC daily HNT close rose from $0.1909 on August 24 to $0.7663 on August 30, roughly quadrupling before T-Mobile traffic was removed; it closed August 31 at $0.6440.
  • HIP 150 redirected Nova's Service Provider rewards to data deployers, moving the baseline Mobile data allocation from 70% to 94%.
  • The August 31 earnings rate reflects three concurrent drivers: a higher HNT price, HIP 150's larger data-transfer pool, and fewer rewardable bytes after T-Mobile traffic stopped.
  • The official post and call did not name the carrier or integrator; the Helium community identified them as T-Mobile and Ameriband.
  • Other carrier relationships, including AT&T and Telefonica/Movistar, were said to be unaffected.
  • HIP 150 voting was scheduled to close August 31, 2026 at 18:11 UTC.
  • At a $0.10/GB payer rate, HIP 150's 80% target minimum is $0.08 per rewardable GB, up from the HIP 149 target of $0.05.
  • Reward multipliers are not automatic; they require Helium Plus participation and commercial approval for the location.
  • Carrier submission lists were described as weekly, with processing expected to return to about one week after recent delays.

FAQ

Why did my hotspot lose T-Mobile offload?

All T-Mobile selections were removed from Helium hotspots network-wide on August 31, 2026 because the offload integration through Ameriband ended. This was not an eligibility problem affecting only your hotspot, and AT&T offload remains active. If your hotspot lost T-Mobile before August 31, an earlier location reassertion or individual carrier-selection change may have been a separate cause.

Sources

These notes and the transcript were prepared with AI assistance. Sources are listed for verification.