Störungsverlauf von Helium

1. 12. Juli 2026 um 16:53 UTCinvestigating

   We’re observing an increase in hotspot heartbeat issues and are currently investigating. We will continue to keep the community updated.

2. 13. Juli 2026 um 15:23 UTCresolved

   We've resolved an issue affecting network connectivity, caused by a certificate issue. The certificate has been corrected, and we've implemented additional monitoring to detect and prevent this type of issue going forward.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. April 2026 um 17:25 UTCresolved

   Some Helium Mobile Hotspots had an issue where devices could connect to WiFi but couldn’t actually use the internet, due to a problem on those specific units, while the overall network was working normally. A fix is being worked on for affected hotspots - if you experience this behaviour, restarting your hotspot is advised.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. März 2026 um 02:04 UTCidentified

   A performance issue is affecting Helium Packet Router performance in the Frankfurt region. This may affect IoT device message delivery in Europe. The team has identified the issue and is scaling resources to resolve the issue.

2. 11. März 2026 um 02:44 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11. März 2026 um 03:20 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Februar 2026 um 16:24 UTCresolved

   During the IMS-Prod upgrade, services experienced a brief outage of roughly 15–20 minutes due to a load balancer and DNS issue introduced during the update. This impacted the Hotspot dashboard and related IMS services. The issue was identified and resolved, and all systems are now fully operational.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. Januar 2026 um 17:57 UTCidentified

   An upstream service is causing some Hotspots to fail to load. The team is investigating the issue and will deploy a fix shortly.

2. 27. Januar 2026 um 19:54 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. November 2025 um 14:36 UTCidentified

   Due to the current Cloudflare outage worldwide, some services are currently unavailable. We are monitoring the situation and will post updates here as they become available.

2. 18. November 2025 um 15:06 UTCresolved

   Cloudflare services have recovered.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. November 2025 um 00:57 UTCinvestigating

   We’re seeing reduced traffic from one carrier starting yesterday. Other carriers are unaffected. We are collaborating with the carrier to understand the behavior. We’ll update once we have more details.

2. 15. November 2025 um 17:54 UTCidentified

   The issue appears to stem from a recent software update on the carrier's side and we’re actively collaborating on a fix with our partner. Traffic from other carriers remains unaffected. We’ll share more updates as progress continues but we're not expecting any updates until Monday at the earliest.

3. 23. November 2025 um 00:01 UTCresolved

   The technical issue impacting service has been resolved. Carrier traffic has stabilized. We’ll continue monitoring to ensure everything remains nominal.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. November 2025 um 14:38 UTCinvestigating

   We’re currently investigating a Brownfield service degradation. The issue appears to be linked to a connection problem between RADIUS AAA instances following the latest radiator-rs deployment. Our team is working to identify and resolve the problem as quickly as possible. Further updates will be shared here once more information is available.

2. 7. November 2025 um 14:27 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Oktober 2025 um 23:30 UTCinvestigating

   We are aware of an issue affecting access to the Helium Mobile Builder Dashboard. Some users may be unable to log in, while others who can access their dashboards are experiencing issues viewing hotspot telemetry data. This appears to be a visual-only issue and does not affect hotspot performance or reward earnings. The team is actively investigating the cause and working on a resolution. We expect to provide an update by end of day tomorrow (October 17, 2025).

2. 16. Oktober 2025 um 23:32 UTCinvestigating

   Note that the issue may affect explorer statistics related to data transferred and daily active users. . We are continuing to investigate this issue.

3. 16. Oktober 2025 um 23:40 UTCinvestigating

   We are continuing to investigate this issue.

4. 17. Oktober 2025 um 14:47 UTCresolved

   This issue was resolved

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Oktober 2025 um 18:06 UTCidentified

   Native token swap functionality in the Helium Wallet app is currently unavailable due to a downstream change with Jupiter's APIs. All users of current versions (v2.14.16 and prior) of Helium Wallet will have to use the dApp browser for swaps until v2.14.17 is implemented, deployed, and approved by App Stores.

2. 1. Oktober 2025 um 19:35 UTCidentified

   The fix for native swaps (v2.14.17) is currently in App Store review on both Android and iOS. We’ll update once it’s approved and live.

3. 1. Oktober 2025 um 21:23 UTCresolved

   Native swap functionality has been restored with the release of Helium Wallet v2.14.17, now live on both the App Store (iOS) and Google Play (Android). Please update to the latest version to resume in-app swaps.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. September 2025 um 21:22 UTCidentified

   We are currently investigating reports of mobile onboarding failures. Affected users may see the following error when attempting to onboard: {"InstructionError":[2,{"Custom":6016}]} Impact: All new Mobile onboards are currently failing. Existing Mobile users are unaffected.

2. 2. September 2025 um 22:01 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. August 2025 um 22:11 UTCidentified

   Following the recent Mobile Oracle infrastructure migration, the team has noticed that a subset of HMHs are failing to submit speed tests. The lack of speed tests will prevent a Hotspot from receiving Proof of Coverage rewards. A backend patch has been applied which will likely address the issue without operator intervention. However, if you notice your HMH is failing to submit speed tests, a simple reboot should resolve the issue.

2. 3. September 2025 um 13:47 UTCmonitoring

   A backend patch has been applied to address issues with Hotspots failing to submit speed tests. If you’re still seeing problems, a reboot should fix it. We’ll continue to monitor.

3. 7. Oktober 2025 um 19:04 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. August 2025 um 17:23 UTCinvestigating

   We are currently investigating reports of Error 522 (Connection Timeout) affecting some users during onboarding and hotspot updates. Impact: users may see a timeout or error message when attempting to complete payments or update antenna information. Scope: Issue appears intermittent and does not affect all devices. Current Status: Our engineering team has identified this as potentially related to recent application updates. A fix is being tested. We’ll provide updates here as we learn more. Thank you for your patience.

2. 22. August 2025 um 18:28 UTCresolved

   Resolved: Error 522 (Connection Timeout) We’ll continue monitoring to ensure stability. Thank you for your patience while we worked to resolve this.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juni 2025 um 17:02 UTCmonitoring

   We are currently investigating an issue preventing FreedomFi AGWs from being onboarded as IoT Hotspots. We are assessing the impact and determining next steps, including restoring onboarding capabilities. Current Status: * FreedomFi AGW onboarding temporarily unavailable. * Root cause identified Further updates will be shared as the situation develops. Please reach out to support if you are affected.

2. 13. August 2025 um 19:27 UTCresolved

   This issue has been resolved

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. April 2025 um 19:07 UTCinvestigating

   The core developers are investigating an outage in Hotspot rewards claiming in the Helium Wallet app. This appears to be due to a downstream dependency on an infrastructure provider that helps index Helium data for clients like the Helium Wallet.

2. 8. April 2025 um 21:29 UTCidentified

   Core developers have identified the downstream infrastructure provider and while they are working on a fix, we are also applying some mitigation. This will require an upgrade of the Helium Wallet app. We are starting the process to update metadata, the app, and submit it to the App Stores for review.

3. 8. April 2025 um 23:15 UTCresolved

   The downstream storage provider has resolved their outage and we are closing this issue. That said, a new version of the Helium Wallet app will be released in the next 24 hours (assuming app store reviews are expedited) that should prevent this particular impact in the future.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 4. Mai 2024 um 05:29 UTCidentified

   Due to Solana network congestion, transactions may fail or be delayed. For example, Hotspot reward claims may take several minutes to complete. Keep the wallet app open after hitting claim button or try again later.

2. 9. Mai 2024 um 16:45 UTCresolved

   The Helium Foundation has deployed additional Solana RPC infrastructure in order to support the growing Helium Wallet user base.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. April 2024 um 00:18 UTCidentified

   Due to high Solana congestion, transactions may fail or be delayed. Please retry failed transactions.

2. 2. Mai 2024 um 16:54 UTCresolved

   This incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. April 2024 um 14:49 UTCinvestigating

   As reported by the community, The Foundation Console has been dropping device uplinks since approximately 1:30 UTC. We are currently looking into it.

2. 3. April 2024 um 15:22 UTCresolved

   We identified the root cause as the Foundation Console's router failing to reboot as expected after erroring. We have manually rebooted said router and packets are now correctly being received.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. Februar 2024 um 11:31 UTCidentified

   As noted on status.solana.com, the Solana network is currently experiencing a chain halt which may affect some activity for Helium network users. Notably, deployers will not be able to onboard or move Hotspots and token holders may not be able to perform transfers or participate in other on-chain activity. Rest assured that Solana validators and core developers are working on resuming block production and that Helium oracle activity is not affected.

2. 6. Februar 2024 um 11:37 UTCidentified

   Engineers from across the Solana ecosystem are readying a new validator software release, which includes a patch to address an issue which caused the cluster to halt.

3. 6. Februar 2024 um 12:12 UTCidentified

   Solana validators have begun a coordinated restart with an updated release version. You can follow status here: https://stakewiz.com/restart

4. 6. Februar 2024 um 15:07 UTCmonitoring

   Block production has resumed on Solana. We will continue to monitor over the next few hours.

5. 6. Februar 2024 um 15:26 UTCresolved

   We join the Solana community in thanking validator operators and core developers for their firefighting over the past few hours.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. November 2023 um 15:50 UTCresolved

   The automated job that was supposed to end the November 13th epoch (19,674) at UTC midnight stalled due to a dropped transaction. The job continued to wait for confirmation on a transaction that was never picked up by Solana. The epoch was manually ended by Core Developers at 15:30 UTC. No further action is needed. The team will be improving alerting to ensure we are notified earlier when epochs fail to close. Additionally, they will be repairing the automated job to include a timeout on transaction confirmations.

Automatisch aus der offiziellen Störungsmeldung übersetzt.