Documentation
Hopbits docs
Hopbits is a network of independent nodes that measure whether a service is up, how fast it answers, and where an IP address really is. These pages show how to run a node and how to use what the network measures.
Two sides of one network
Operators run a small node on a home or datacenter connection. The node carries out measurement jobs, and the operator earns points for the time it is online.
Businesses use the measurements. A monitor in the dashboard, or a request to the API, asks nodes in chosen countries to check a target and reports what they saw.
One account covers both. You can run nodes, watch services, or do both from the same sign-in, and manage password, email verification, and referrals in Account settings.
What a node measures
| Check | What the node does | What it tells you |
|---|---|---|
| HTTP | Sends one GET or HEAD request | Whether the service answers, with which status, and how long each phase took |
| TCP connect | Opens a connection and closes it at once | Whether the port can be reached, and how long connecting took |
| Ping | Sends a few ICMP echo packets | The round-trip time from that place to the target |
A node is not a proxy. It never carries anyone else's traffic. What a node will never do lists the limits built into it.
Where to ask
The quickest answers are in the Hopbits Discord. For anything private, write to [email protected].