Skip to content
Node troubleshooting

Why bandwidth-sharing nodes go offline

If your node goes offline, first check that the device is awake, AntGain is running, and internet access works. Then review recent network changes and confirm your client is supported.

Common causes

Work from observable device and network state instead of guessing from the word “offline.”

Check the device, the app, your local network, and any service-provider outage. The offline status alone does not identify the cause.

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.

The AntGain process is no longer running

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.

The local network changed

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.

Router, NAT, or upstream state changed

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.

Connectivity exists but is unstable

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.

The installed client is no longer supported

Platform support can change by release. Check the current download page for supported platforms and installation requirements.

Recovery checklist

Check the lowest-risk causes first.

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.

  1. 1

    Confirm the device is awake and has normal internet access outside AntGain.

  2. 2

    Confirm the AntGain application or node process is actually running after login or restart.

  3. 3

    Check the current download page to confirm your platform is supported before reinstalling or changing packages.

  4. 4

    If the network recently changed, allow the node to reconnect rather than assuming the old session should remain valid.

  5. 5

    Check whether a VPN, firewall, captive portal, router restart, or upstream outage coincided with the disconnect.

  6. 6

    Check your account or device view to confirm whether AntGain currently sees the node online.

FAQ

Node offline troubleshooting questions

Answers keep ordinary internet access, node state, network topology, release support, traffic, and earnings separate.

Does an offline AntGain node mean my internet connection is broken?
No. A node can be offline while ordinary browsing still works. The application process, device power state, network transition, router state or current release path can interrupt the AntGain session independently of basic web access.
Does keeping a node online guarantee traffic or earnings?
Traffic and earnings vary with demand and successfully recorded activity. Being online does not guarantee income.
Should I open inbound ports on my router to make AntGain work?
Do not change router exposure merely because a node appears offline. Start with the supported AntGain installation and normal outbound connectivity. Only follow port or firewall guidance when it is explicitly documented for the current product and deployment model.
Can several devices behind one router all stay online?
Several devices can connect through one router, but they may share the same public IP. Adding devices alone does not guarantee more traffic or earnings.
Where should I check whether my operating system is currently supported?
Use the current AntGain download page. Platform support can change between releases.
Current release

Ready to reconnect your node?

Check that your client is supported, then confirm in your account whether the node returns online.