• SIX PROBE KINDS
  • LOCAL ISP VIEW
  • SYNCHRONOUS API

Product · Network tests

Test from their side.Right now.

  1. {
  2. "id": "9c1f0e4ab27d4c55a0e3b6d18f2c7a41",
  3. "type": "http", "target": "cloudflare.com",
  4. "status": "finished", "credits_charged": 2,
  5. "results": [
  6. { "country": "DE", "asn": 3320, "network_class": "residential",
  7. "outcome": "ok", "result": { "status_code": 200, "first_byte_us": 14200 } },
  8. { "country": "NL", "asn": 1136, "network_class": "residential",
  9. "outcome": "ok", "result": { "status_code": 200, "first_byte_us": 19800 } },
  10. { "country": "SG", "asn": 4755, "network_class": "datacenter",
  11. "outcome": "timeout" }
  12. ]
  13. }

Send one test from nodes in the countries you choose, over home, mobile or datacenter connections: an HTTP request, a TCP connect, a ping, a DNS lookup or a trace of the route. Each node answers with what it saw and how long it took.

Why

It works from your desk. That is one connection.

A customer in another country reaches you over another provider, another route and another DNS server.

Another route

Traffic from another country crosses other networks on its way to you. A fault on that road never shows from your office or your cloud region.

Another answer

DNS and caches can hand out different answers in different places. One country may be sent to a server that is slow, or gone.

Another kind of line

Home and mobile connections behave differently from a datacenter. A test from a cloud server says little about them.

How it works

Three steps. One answer from every node.

Run a test in the Console's Playground, with one API call, or from the command line.

  1. Pick.

    Choose what to test and from where: up to ten places in one test, each by country, by kind of connection, or by one provider's network.

  2. Run.

    Nodes in every place run the test at the same time. In one place, no two of them belong to the same operator or the same block of addresses.

  3. Read.

    Each node answers with what it saw: a status code and where the time went, lost packets, DNS records, or every hop on the route.

What you get

What you get. In every package, the free one too.

No feature is held back for a larger plan. A package is its credits and nothing else.

Six kinds of test

An HTTP request, a TCP connect, a ping, a DNS lookup, a traceroute, and MTR, which measures loss and delay at every hop.

Up to ten places at once

One test can ask up to ten countries, with several nodes in each, and brings all the answers back together.

Home, mobile or datacenter

Choose the kind of connection in each place, or name one provider's network.

Where the time went

An HTTP answer splits the time into connecting, the TLS handshake and the first byte, and shows the status code and any redirect.

Which server answered

Ask for response headers, such as the cache status, and see which server or cache answered in each country.

DNS as they see it

Look a name up through each node's own provider, or through a public resolver, and compare the records each place gets.

The route, hop by hop

A trace names the network and the country of each public router on the way, so you see where a route leaves the road you expected.

Independent nodes

In one place a test never uses two nodes of one operator or one address block, so no single network can colour the result.

Pay for answers only

One credit for each node that answers, two for MTR. You can ask what a test will cost first, and a test that gets no answer is free.

In practice

Questions it answers. In the time it takes to ask.

Four situations teams bring to it.

Performance engineers

Your own numbers say the response time is fine, and one market overseas keeps complaining.

Run one request from that country, over home connections and from a datacenter beside them. The answers show where the time goes: connecting, the handshake, or the wait for the first byte.

Support teams

A ticket says the site does not load. It loads for you.

Test the same address from their country and their kind of connection, or from their provider's network, and see the status code or the error they got.

Platform teams

You moved a record an hour ago, and some visitors still land on the old server.

Look the name up through the local providers' resolvers in several countries, and compare what they return with a public resolver's answer.

Release engineers

A deploy passes its tests in the build and breaks for users in one region.

Run a test from the command line after every deploy. It fails the build when the status, the response time or the number of healthy places is below what you set.

Tools

In the tools you have. Playground, API and command line.

Try a test in the Console's Playground first. The same test is one call to the REST API, and one command in a build.

REST APIMeasure
POST 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" }  ]}
Command linehopbits probe
# After a deploy: fail the build unless three countries answer 200 fast enough.$ hopbits probe https://api.example.com/healthz --from DE,US,SG --network residential --expect-status 200 --max-p95 500ms # What do local providers' resolvers return in each country?$ hopbits probe _dmarc.example.com --type dns --qtype TXT --resolver isp --from DE,US,NL # Loss and delay at every hop of the route.$ hopbits probe example.com --type mtr --cycles 5 --proto udp --from DE,US

Cost

What it costs. Free to start.

Every account gets 1,000 free credits a day. That is up to 1,000 answers from nodes, every day. More credits come by the month or as a one-time top-up.

1 creditAn answer from one node
2 creditsAn MTR answer from one node
FreeA test that gets no answer
1,000Free credits, every day

The packages

  • Free$01,000 credits a day
  • Starter$12 a month150,000 credits a month
  • Team$39 a month600,000 credits a month

Questions

Good questions. Clear answers.

More in the docsHow tests work

Other productsUptime monitoringIP location

Do I have to own the site I test?

No. Any public site can be tested on its standard web ports. Other ports need a site you have verified.

How many places can one test use?

Up to ten places, with up to ten nodes in each, and fifty nodes in all.

Which nodes run my test?

Nodes that are online in the places you chose, picked afresh for every test. In one place, no two of them share an operator or a block of addresses.

Can I see how large the network is?

Yes. The public status page shows the network live, by country, and the Playground shows how many nodes can take part before you run a test.

What does a test cost?

One credit for each node that answers, two for MTR. You can ask what a test will cost before you run it, and a test that gets no answer is free.

Does the site I test see the requests?

Yes. Every HTTP test says who it is, and the owner of a site can ask not to be tested.

Get started

Try it on your own site.
It is free to start.

Create an account and you have 1,000 credits every day. No purchase. No wallet.