• MULTI-VANTAGE
  • RESIDENTIAL & DC
  • QUORUM VERIFIED

Product · Uptime monitoring

Know when it is down.And for whom.

  1. {
  2. "id": "chk_4b1d9e07a3c2f581",
  3. "name": "Cloudflare Edge",
  4. "type": "http", "target": "cloudflare.com",
  5. "interval_seconds": 60, "state": "up",
  6. "uptime_24h": 99.98, "p50_ms": 18, "p95_ms": 42,
  7. "locations": ["DE", "US", "SG"],
  8. "latest_runs": [
  9. { "country": "DE", "asn": 3320, "status_code": 200, "first_byte_us": 14200 },
  10. { "country": "US", "asn": 7922, "status_code": 200, "first_byte_us": 21800 },
  11. { "country": "SG", "asn": 4755, "status_code": 200, "first_byte_us": 38900 }
  12. ]
  13. }

Hopbits checks your site or API on a schedule, from home connections and datacenters in the countries you choose. Several nodes have to agree before it calls an outage, and it tells you whether one country fails or all of them.

Why

A single check tells one story. Your users live in many.

Most monitors look at your site from a few datacenters. That is not where your customers are.

Blind spots

A check from one place sees one route to your site. When a provider in another country cannot reach you, it stays green and you hear about it from a customer.

The wrong kind of line

People reach you over home connections. Hopbits checks from those, and from datacenters, so you see both the user's road and a steady baseline.

False alarms

One bad connection should never wake you. Hopbits asks several nodes on different networks, and calls an outage only when they agree.

How it works

Three steps. Then it runs by itself.

Set a monitor up in the Console, through the API, or from a file in your repository.

  1. Choose.

    Give it an address, how often to check, and up to three countries. Or let it use any node that is free.

  2. Check.

    On every run, up to three nodes in each country try to reach it, each on a different network. A country counts as down only when at least two fail and a second check from other nodes agrees.

  3. Alert.

    Every change of state goes out by email and, if you want, as a signed webhook. When two runs in a row are fine again, the all-clear follows.

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.

The countries you choose

Pick one to three countries where your users are. Partial means one of them cannot reach you. Down means two or more of them, or all.

Home and datacenter nodes

Checks run from real home connections and from datacenters, never from one operator alone.

As often as every 30 seconds

From once an hour to every five minutes on any site. Every 60 or 30 seconds on a domain you have verified.

HTTP, TCP and ping

A light HTTP check works on any site. A full HTTP GET, a TCP connect and ping need a domain you have verified.

A public status page

Show your visitors whether each service is up, with 90 days of history and your outages. One page for each website or project, at an address you choose.

Email and signed webhooks

Each change reaches your inbox and your own tools. The webhook is signed, so the tool that receives it can trust it.

A day of response times

Every monitor keeps the last 24 hours: the typical response time and the slow end, by country, with the latest answer from each node.

An honest uptime figure

Uptime counts only the runs where enough nodes answered. A check that could not run never lowers your figure and never raises an alarm.

Monitors as code

Keep your monitors in a file beside your code, see what a change will do, and apply it from your build with the Hopbits command line tool.

In practice

Questions it answers. Before a customer asks them.

Four situations teams bring to it.

SaaS and API teams

Your own office reaches the checkout without trouble, and the support inbox fills with complaints from one country.

The monitor turns Partial: one of your countries cannot reach it, the others can. You know it is a regional problem within one run, and where to look.

Teams building on other services

You build on a cloud, a CDN or a payment API, and its status page is still green while your errors climb.

Watch its public endpoint with a light check. When it fails you see it yourself, and one test from more countries shows how far the failure reaches.

Web3 and infrastructure teams

You run an RPC endpoint or a gateway that people in many countries depend on every minute.

On a domain you have verified, check it over HTTP, TCP or ping as often as every 30 seconds, from the countries that matter to you.

On-call engineers

An outage at night is found in the morning, from a customer's message.

Every change of state goes out at once, by email and as a signed webhook, so your own tools can open a ticket or page whoever is on call.

Tools

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

Everything the Console does is one call to the REST API. Teams who keep their setup in a repository write their monitors in a file and apply it from their build.

REST APIMonitor
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}
hopbits.yamlCommand line
version: 1 monitors:  - key: marketing-site    name: Marketing Site    type: http    method: HEAD    target: https://www.example.com    interval: 5m    locations: [DE, US, SG]    alert_email: true
# See what a change will do. Nothing is changed.$ hopbits plan -f hopbits.yaml # Make it so.$ hopbits apply -f hopbits.yaml

Cost

What it costs. Free to start.

Every account gets 1,000 free credits a day. That keeps one site checked every five minutes from one country, around the clock. More credits come by the month or as a one-time top-up.

Up to 3 creditsA check from one country
864 a dayAt most, for one site every 5 minutes from one country
1,000Free credits, every day
FreeA check that could not run

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 monitors work

Other productsNetwork testsIP location

Can I monitor a site that is not mine?

Yes, with a light check every five minutes to every hour. Checks every minute or every 30 seconds, TCP and ping need a domain you have verified.

What counts as down?

A country counts as down when at least two nodes on different networks cannot reach your site and a second check from other nodes agrees. A node that fails alone never counts against your site.

Does it look at what the page says?

Not today. Any HTTP answer counts as up, an error page included. A monitor tells you whether your site can be reached and how fast it answers.

How do alerts reach Slack or a pager?

Through the webhook. Every change of state is sent, signed, to an address you choose, and your own tool turns it into a message or a page.

Can I show my uptime to my customers?

Yes. Switch on a status page for the monitors you pick: a public page with the state of each service, 90 days of history and your outages. You can have one for each website or project, and showing it uses no credits.

What happens when my credits run out?

Checks wait until you have credits again. The free 1,000 come back every day at 00:00 UTC. A check that was skipped never raises a false alarm.

How many monitors can I add?

As many as you like. They all run on the same credits.

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.