The device sleeps, hibernates, or powers down
A node cannot remain reachable while its host is suspended or off. Laptop lid-close behavior, operating-system sleep timers and energy-saving policies are common places to check first.
Common causes
Check the device, the app, your local network, and any service-provider outage. The offline status alone does not identify the cause.
A node cannot remain reachable while its host is suspended or off. Laptop lid-close behavior, operating-system sleep timers and energy-saving policies are common places to check first.
Closing the application, signing out, stopping a service, an operating-system restart, or a failed background launch can end the node session even while the device itself still has internet access.
Moving between Wi-Fi networks, switching from Ethernet to Wi-Fi, reconnecting a modem, changing VPN or tunnel state, or receiving a new network configuration can interrupt an existing session and require reconnection.
A router restart, changed public IP, or service-provider interruption can break an existing connection. An offline status alone does not identify your NAT type.
Intermittent packet loss, captive portals, DNS problems, weak Wi-Fi or repeated network transitions can make a device look connected to the user while the node cannot keep a stable application session.
Platform support can change by release. Check the current download page for supported platforms and installation requirements.
Recovery checklist
Avoid opening inbound ports, disabling security controls, or changing router exposure just to chase an offline indicator. Verify the host, process, and current release path first.
Confirm the device is awake and has normal internet access outside AntGain.
Confirm the AntGain application or node process is actually running after login or restart.
Check the current download page to confirm your platform is supported before reinstalling or changing packages.
If the network recently changed, allow the node to reconnect rather than assuming the old session should remain valid.
Check whether a VPN, firewall, captive portal, router restart, or upstream outage coincided with the disconnect.
Check your account or device view to confirm whether AntGain currently sees the node online.
After the node reconnects
Restoring connectivity makes the node available again. Traffic and earnings still depend on demand and successfully recorded activity.
Review earnings guidanceTroubleshoot safely
Do not open inbound ports, disable firewalls, or broaden router exposure unless current product-specific documentation explicitly requires a narrowly scoped change.
Review safety and network useFAQ
Answers keep ordinary internet access, node state, network topology, release support, traffic, and earnings separate.
Check that your client is supported, then confirm in your account whether the node returns online.