User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
helium.com · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 273 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:00 | 0 | 0.0 | 108 ms | 0 |
| 09:15 | 0 | 0.0 | 225 ms | 0 |
| 09:30 | 0 | 0.0 | 165 ms | 0 |
| 09:45 | 0 | 0.0 | 136 ms | 0 |
| 10:00 | 0 | 0.0 | 45 ms | 0 |
| 10:15 | 0 | 0.0 | 217 ms | 0 |
| 10:30 | 0 | 0.0 | 131 ms | 0 |
| 10:45 | 0 | 0.0 | 162 ms | 0 |
| 11:00 | 0 | 0.0 | 142 ms | 0 |
| 11:15 | 0 | 0.0 | 109 ms | 0 |
| 11:30 | 0 | 0.0 | 110 ms | 0 |
| 11:45 | 0 | 0.0 | 72 ms | 0 |
| 12:00 | 0 | 0.0 | 211 ms | 0 |
| 12:15 | 0 | 0.0 | 136 ms | 0 |
| 12:30 | 0 | 0.0 | 67 ms | 0 |
| 12:45 | 0 | 0.0 | 78 ms | 0 |
| 13:00 | 0 | 0.0 | 120 ms | 0 |
| 13:15 | 0 | 0.0 | 256 ms | 0 |
| 13:30 | 0 | 0.0 | 122 ms | 0 |
| 13:45 | 0 | 0.0 | 127 ms | 0 |
| 14:00 | 0 | 0.0 | 86 ms | 0 |
| 14:15 | 0 | 0.0 | 154 ms | 0 |
| 14:30 | 0 | 0.0 | 170 ms | 0 |
| 14:45 | 0 | 0.0 | 228 ms | 0 |
| 15:00 | 0 | 0.0 | 198 ms | 0 |
| 15:15 | 0 | 0.0 | 179 ms | 0 |
| 15:30 | 0 | 0.0 | 87 ms | 0 |
| 15:45 | 0 | 0.0 | 125 ms | 0 |
| 16:00 | 0 | 0.0 | 50 ms | 0 |
| 16:15 | 0 | 0.0 | 136 ms | 0 |
| 16:30 | 0 | 0.0 | 101 ms | 0 |
| 16:45 | 0 | 0.0 | 164 ms | 0 |
| 17:00 | 0 | 0.0 | 134 ms | 0 |
| 17:15 | 0 | 0.0 | 58 ms | 0 |
| 17:30 | 0 | 0.0 | 110 ms | 0 |
| 17:45 | 0 | 0.0 | 110 ms | 0 |
| 18:00 | 0 | 0.0 | 147 ms | 0 |
| 18:15 | 0 | 0.0 | 153 ms | 0 |
| 18:30 | 0 | 0.0 | 170 ms | 0 |
| 18:45 | 0 | 0.0 | 159 ms | 0 |
| 19:00 | 0 | 0.0 | 114 ms | 0 |
| 19:15 | 0 | 0.0 | 199 ms | 0 |
| 19:30 | 0 | 0.0 | 131 ms | 0 |
| 19:45 | 0 | 0.0 | 407 ms | 0 |
| 20:00 | 0 | 0.0 | 135 ms | 0 |
| 20:15 | 0 | 0.0 | 222 ms | 0 |
| 20:30 | 0 | 0.0 | 111 ms | 0 |
| 20:45 | 0 | 0.0 | 273 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Helium yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Helium goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Helium alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Helium is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Helium's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.