The internet looks different from every connection. Help us see the whole picture.
Join the network measuring uptime, latency, and IP location from homes and datacenters around the world.
The network
One server can tell you if your website is up. A network can help you see who it’s up for.
Local ISPs. Real last-mile connections. Perspectives beyond the cloud, on the stretch of the route only a home connection travels.
Stable connections. Consistent baselines. More context for every measurement.
Hopbits brings residential and datacenter measurements together, connecting the reliability of infrastructure with the reality of local networks.
Network intelligence
Three signals from one network. Built for a more observable internet.
Up for you. But up for everyone?
A single check only tells one story. Monitor reachability from independent residential and datacenter connections to spot regional outages and confirm what’s actually down.
Find the slow. Before your users do.
See how response times change across cities and networks. Compare home connections with datacenter baselines to understand where performance starts to slip.
Go beyond a pin on a map.
Combine measurements from known reference points to assess where an IP could be. Build confidence in location estimates and flag mismatches in existing IP data.
For node operators
Run a lightweight Linux or Docker node, contribute signed network measurements, and earn contribution points.
Create operator accountFree account · no wallet needed.
Run the Hopbits Linux or Docker client on a supported device.
Help measure reachability, latency, and location signals from your network.
Build a contribution record through validated work and useful coverage.
Measurements the network accepts and other nodes confirm.
Being reachable when a check is scheduled.
Locations and networks that are in demand.
Points are counted for finished UTC days and confirmed after a review period.
For businesses
Turn independent network measurements into decisions about performance, reliability, and location.
Get startedDashboard + API · dollar-based pricing · no wallet required
Run one request from up to ten countries at once, over home or datacenter connections. Each answer shows where the time went: connecting, the TLS handshake, the first byte.
Performance engineersTest your candidate servers from the countries your users live in, and choose by measured latency, not by the map.
Hosting & edge networksProbe the same address from their country and their kind of connection, or from one provider's network, and see the status code or the error they got.
Support teamsRequest a page from a country that should be refused and from one that should not, then compare the status codes and redirects that come back.
Compliance teamsIn each country you pick, three nodes on different networks run the check and two must agree. One bad connection never wakes you, and the alert says whether one country fails or several.
SaaS & API teamsWatch the public endpoints of the cloud, CDN or payment API you build on. When one fails, a test from more countries shows how far the failure reaches.
Teams building on other servicesCheck an RPC endpoint, a gateway or any port on a domain you have verified, over HTTP, TCP or ping, as often as every 30 seconds.
Web3 & infrastructure teamsEvery change of state goes out by email and as a signed webhook, so your own tools can open a ticket or page whoever is on call.
On-call engineersNodes time the replies from the address. Nothing travels faster than light, so each reply limits how far away it can be. Name the country it claims, and the answer says whether that is plausible.
Fraud & risk teamsEach answer puts the measured area beside what an IP database says, with a confidence and a radius, so records that have gone stale stand out.
Geolocation data teamsBefore you rely on a hosting region or a VPN exit, measure where the machine can physically be.
Hosting buyers & reviewersThe answer also names the operator of the address and says whether it is a home, mobile or datacenter line, or one address announced from many places.
IP intelligence teamsPOST https://api.hopbits.io/v1/measurements{ "type": "http", "target": "api.example.com", "locations": [ { "country": "NL", "network": "residential", "limit": 1 }, { "country": "DE", "network": "datacenter", "limit": 1 }, { "country": "SG", "network": "datacenter", "limit": 1 } ], "params": { "method": "HEAD", "path": "/healthz" }}200 OK GET /v1/measurements/9c1f0e4ab27d4c55a0e3b6d18f2c7a41?wait=10{ "status": "finished", "target": "api.example.com", "credits_charged": 2, "results": [ { "country": "NL", "network_class": "residential", "outcome": "ok", "result": { "status_code": 200, "phases": { "first_byte_us": 42400 } } }, { "country": "DE", "network_class": "datacenter", "outcome": "ok", "result": { "status_code": 200, "phases": { "first_byte_us": 18100 } } }, { "country": "SG", "network_class": "datacenter", "outcome": "timeout" } ]}POST https://api.hopbits.io/v1/checks{ "name": "Public API", "type": "http", "target": "api.example.com", "method": "HEAD", "path": "/healthz", "interval_seconds": 300, "locations": ["DE", "US", "SG"]}201 Created{ "id": "chk_4b1d9e07a3c2f581", "name": "Public API", "type": "http", "target": "api.example.com", "method": "HEAD", "path": "/healthz", "interval_seconds": 300, "locations": ["DE", "US", "SG"], "alert_email": true, "verified": false, "paused": false}POST https://api.hopbits.io/v1/geolocate{ "target": "203.0.113.42", "mode": "fresh", "claim": { "country": "US" }}200 OK{ "ip": "203.0.113.42", "confidence": "high", "radius_km": 118, "country": "DE", "city": "Frankfurt am Main", "target_class": "datacenter", "method": "cbg_icmp", "vps_used": 4, "claim_check": { "verdict": "implausible" }, "credits_charged": 6}The road ahead
We’re scaling in stages. Create an account and build with us.
Onboard the first Linux and Docker operators and business monitoring teams.
Scale node coverage, validate cross-ASN measurements, and refine contribution points.
Expand geolocation confidence APIs, webhook integrations, and regional benchmarking.
Reach more countries, cities, and local ISPs so every check has a closer point of view.
A little more context
Straight answers on how Hopbits works for Linux and Docker node operators and business teams.
Hopbits brings together independent residential and datacenter nodes to measure website uptime, regional latency, and IP location signals. Node operators contribute measurements and earn points; businesses use the resulting insights through a dashboard and API.
Yes. First-release access uses the Linux and Docker node client. Create a free Hopbits account and open your operator dashboard to link a single node via an 8-character pairing code or provision multiple hosts with a 24-hour enrolment token.
Points reward the hours your node is online and the measurements it completes that the network accepts. Your operator dashboard shows what each node has earned, and each finished day is confirmed after a review period.
Yes. Home connections add local ISP viewpoints that are difficult to obtain from cloud providers alone, while datacenter nodes offer reliable reference baselines. Both contribute directly to multi-perspective checks.
No. The Linux and Docker node client is strictly for controlled, cryptographically signed network measurements, never general-purpose proxy traffic or customer browsing. Permissions, daily bandwidth caps, and supported check types are bounded inside the client.
Hopbits estimates plausible geographic areas and confidence levels using round-trip measurements from multiple calibrated reference points. Because network routing affects latency, measurements narrow regions and flag stale GeoIP mismatches rather than claiming an exact street address.
No. Hopbits provides a conventional web dashboard and REST API with US-dollar plans. No crypto wallet is required for operators or business customers.
Get started
Create one account to run Linux and Docker nodes, monitor your services, or both. No purchase. No wallet.