Mining problems can develop gradually: an ASIC goes offline, a rack loses its network connection, or a worker’s rejection rate rises. Without monitoring, these changes may go unnoticed until an operator checks the equipment or pool dashboard.
ViaBTC’s alert features help operators notice changes in pool-observed hashrate, offline workers, and elevated rejection rates. Notifications are available through email, app push, and Telegram, depending on the configuration. Alerts help identify when to investigate; the miner’s local status and logs help explain what happened.
What ViaBTC Hashrate Alerts Monitor
The main signals serve different purposes:
- Low hashrate: A decline in pool-observed hashrate reaches the configured alert threshold.
- Worker offline: A worker meets the system’s offline alert condition.
- High rejection rate: The rejection rate reaches the configured alert level.
Available settings depend on the alert type and configuration route. Do not assume that creating worker groups also creates separate group-level alert controls.
Pool-observed hashrate is an estimate based on submitted shares, not a direct reading from the ASIC. ViaBTC documents its real-time hashrate as an average over the previous 10 minutes and its daily hashrate as an average over the previous 24 hours. A miner’s local display may use a different averaging period or refresh rate, so a temporary difference does not necessarily indicate a fault. See ViaBTC’s explanation of pool and local hashrate.
How to Set Up ViaBTC Hashrate Alerts
To configure alerts through the web dashboard:
- Sign in to your ViaBTC account.
- Select Pool and open Dashboard.
- Select Alert Settings.
- Configure the available parameters for the alert you want to enable.
- Click Confirm to save the parameters.
- Under Notification Method, configure the receiving email address or Telegram account as applicable.
ViaBTC lists email, app push, and Telegram as supported notification methods. Follow the options shown in your account for the selected alert. The official notification setup guide includes screenshots of the configuration process.
Receive alerts through Telegram
Telegram requires a linked Chat ID. ViaBTC’s guide directs users to open Account Management → Notifications, access @ViaBTC_Official_Bot, obtain a Chat ID, then enter and save it in the notification settings.
Worker-offline and worker rejection-rate alerts can also be sent to a Telegram group. Add the official bot to the group, obtain the group’s Chat ID, and save it in ViaBTC’s settings, preserving its leading minus sign. This lets team members receive notifications without sharing the main account login. Follow the official Telegram setup guide for the complete instructions.
How to Set Up Watcher URL Alerts in the ViaBTC App
Watcher URL alerts let someone with an observer link configure monitoring notifications without using the main account login. ViaBTC currently documents this feature as app-only, with support for worker-offline and worker rejection-rate alerts.
To enable them:
- Open the ViaBTC App and go to My → Watcher → Favorites.
- Tap the Edit icon for the relevant Watcher URL.
- Open Alert Settings.
- Under Account List, select the account to monitor.
- Enable the required alert types: worker offline, worker rejection rate, or both.
- If needed, set a Do Not Disturb time range during which notifications will not be sent.
Share Watcher URLs only with people authorized to view the linked monitoring information. See ViaBTC’s Watcher URL alert guide for screenshots and feature details.
Organize Workers Before Choosing Thresholds
Give each ASIC a distinct worker name so that an affected worker can be traced to a physical machine. Worker groups can help organize a rack, room, site, or hardware batch on the Workers page.
ViaBTC documents three worker status labels:
| Status | Meaning |
|---|---|
| Active | The worker is connected and submitting work to the pool. |
| Offline | The worker has had no hashrate for 20 minutes to one day. |
| Inactive | The worker has had no hashrate for more than one day. |
These dashboard status periods are separate from the cadence at which alert conditions are checked. For grouping and status details, see How to Manage Workers.
How to Choose Alert Thresholds
Use the available settings for the selected alert and the operation’s normal pool-side performance as your starting point.
- Use observed hashrate, not only the ASIC’s rated hashrate. Allow for normal short-window variation in share submissions as well as changes in operating conditions.
- Account for planned downtime. Maintenance, electricity-price curtailment, and startup periods can reduce reported hashrate without indicating an unexpected fault.
- Compare equivalent periods. A 10-minute pool estimate and a local average covering several days do not provide a like-for-like comparison.
- Investigate an unhealthy baseline. A consistently elevated rejection rate should not be treated as acceptable simply because it is familiar. Review the connection, miner logs, and operating conditions before setting a threshold that would hide the problem.
There is no single alert percentage suitable for every deployment. ViaBTC’s rejection-rate troubleshooting guidance provides platform context, but it should not be treated as a universal alert-setting prescription.
How Often Are Alert Conditions Checked?
The Watcher URL guide explicitly documents these check intervals:
| Alert type | Documented check interval |
|---|---|
| Worker offline | Every 10 minutes |
| Worker rejection rate | Every hour |
ViaBTC’s September 2025 hashrate alert upgrade announcement also lists these intervals under its alert-type improvements. It states that notifications follow the configured alert frequency and include the affected workers.
A check interval is not a guaranteed time from an outage to notification. Timing also depends on when the condition qualifies for an alert, when the next check runs, the configured notification frequency, and any Do Not Disturb period. Do not assume that the same cadence applies to every alert type.
What to Check After an Alert Arrives
Start by identifying the affected account or workers, then compare the pool data with the miner’s local status.
| Alert signal | First checks | Possible causes to investigate |
|---|---|---|
| Hashrate drop | Check which workers account for the decline; compare equivalent measurement periods and local miner status. | Power interruption, overheating, hashboard or fan issues, firmware behavior, network instability, or pool configuration errors. |
| Worker offline | Confirm whether the worker was intentionally stopped; check power and the miner’s connection status. | Power loss, network outage, incorrect Stratum URL or worker configuration, or a miner restart. |
| Elevated rejection rate | Review the trend, miner logs, and connection to the pool. | Latency, packet loss, unstable connections, firmware issues, overheating, or unsuitable mining settings. |
For a machine that is running but appears offline or inactive, ViaBTC recommends checking configuration, whether the miner has been running long enough to submit data, network connectivity, and possible idling. See the offline or inactive worker troubleshooting guide.
If rejection remains high after checking configuration and connectivity, consult ViaBTC’s rejection-rate guidance and contact support with the affected worker details and relevant logs.
Common Mistakes to Avoid
- Setting thresholds too close to normal fluctuations. Repeated unnecessary alerts can make meaningful notifications easier to overlook.
- Forgetting to restore monitoring after maintenance. If alerts are disabled, make re-enabling them part of the maintenance checklist. Set Do Not Disturb periods deliberately.
- Assuming one notification identifies the cause. An alert indicates a monitored condition; local checks are still needed to determine why it occurred.
Conclusion
ViaBTC Hashrate Alerts help operators notice mining issues sooner. Configure the relevant alerts and delivery method, use clear worker names, and choose thresholds based on healthy pool-side performance. When a notification arrives, use the affected worker details and local miner data to guide troubleshooting.
FAQ
Does a hashrate alert mean my ASIC is faulty?
No. Reduced pool-observed hashrate can result from a hardware problem, network interruption, planned downtime, or normal short-window variation. A difference between the local display and pool dashboard does not itself trigger the alert; the configured pool-side condition does.
Why does my miner’s hashrate differ from the ViaBTC dashboard?
The figures may use different measurement methods and periods. ViaBTC documents a 10-minute window for real-time pool hashrate and a previous-24-hour window for daily hashrate. Compare similar periods before interpreting a difference as lost performance.
Should my team use Telegram or Watcher URL alerts?
Telegram group alerts can deliver worker-offline and rejection-rate notifications to multiple recipients. Watcher URL alerts let an observer-link holder configure those alert types in the ViaBTC App. Choose according to whether team members need shared notifications, access to monitoring information, or both.
What rejection-rate threshold should I use?
Choose from the available settings using normal, healthy performance as context. Investigate persistent or sudden increases instead of raising the threshold merely to silence alerts. A historical baseline is useful evidence, but it is not proof that the connection or miner is operating well.
Will I receive an offline alert within 10 minutes?
The documented 10-minute interval is a check cadence, not an end-to-end notification guarantee. Offline qualification, check timing, notification frequency, and Do Not Disturb settings can affect when a notification is sent.