Uptime

What our network actually did

Every number on this page is measured, from outside our network, by a machine that runs none of the things it is watching. We started measuring continuously on 2026-09-10, so the record is short. We would rather publish a short honest record than a long confident one.

Availability

Sign-up, sign-in and the control plane

99.9297%since 2026-09-10

Everything a customer needs in order to buy an address, sign in, enrol a machine or change their plan — fetched from outside our network, through both hubs, every 30 seconds.

Since we started measuring	99.9297% (42m 30s down over 120,889 checks) plus 5m 53s when the watchdog was not running — not counted either way
Last 30 days	99.9381% (26m 30s down over 85,651 checks)
Last 7 days	99.9691% (3 minutes down over 19,411 checks)

Computed from these 18 checks, all of which must pass: auth.login, auth.oidc, auth.token, deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

tunnelnet.com

99.5111%since 2026-09-10

The public site and its guides. It runs on a different machine at a different provider from the control plane, so it is measured separately — and it stays up when the control plane does not.

Since we started measuring	99.5111% (4h 55m down over 120,889 checks) plus 5m 53s when the watchdog was not running — not counted either way
Last 30 days	99.31% (4h 55m down over 85,651 checks)
Last 7 days	100% (0 seconds down over 19,411 checks)

Computed from these 4 checks, all of which must pass: com.guide, com.guides, com.pricing, com.root

TunnelNet Monitoring

99.9497%since 2026-09-21

The monitoring product itself — whether its API is reachable from the internet through both hubs, and whether customer checks are actually being probed. Measured from a machine that runs none of it.

Since we started measuring	99.9497% (23 minutes down over 91,411 checks)
Last 30 days	99.9521% (20m 30s down over 85,651 checks)
Last 7 days	99.9794% (2 minutes down over 19,411 checks)

Computed from these 3 checks, all of which must pass: mon.api.ewr-1, mon.api.mono-1, mon.prober. This surface has only been measured since 2026-09-21 — earlier cycles are not counted for it, because a check that did not exist cannot have passed.

Every incident, including the ones we caused

This is the complete list for the period above — not a selection. Four of the entries below are our own doing, marked “we did this on purpose”: auth hardening (2026-09-10), chaos drill (2026-09-16), release (2026-09-17) and release (2026-09-25). They are counted against us at full weight, because a customer sitting in front of the site during a drill has exactly the outage a customer sitting in front of it during a real fault does.

Sign-up, sign-in and the control plane

2026-10-21 09:00Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.pricing.ewr-1, mesh.healthz.ewr-1

2026-10-20 00:45Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.login.mono-1

2026-10-19 02:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-10-16 23:08Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mesh.healthz.ewr-1

2026-10-16 16:39Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-10-16 01:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-10-15 23:42Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.login.ewr-1, io.root.ewr-1, io.root.mono-1

2026-10-12 22:28Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-12 15:21Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-12 03:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.docs.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-10-12 02:40Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-09 23:56Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-09 00:02Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.healthz.ewr-1, io.pricing.ewr-1, mesh.healthz.ewr-1

2026-10-06 22:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-10-06 21:22Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.mono-1, io.docs.ewr-1, io.login.ewr-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-10-06 21:20Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-06 11:45Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.mono-1, io.pricing.ewr-1, io.root.ewr-1, mesh.healthz.ewr-1

2026-10-06 01:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-05 14:36Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.healthz.ewr-1, io.pricing.ewr-1, mesh.healthz.ewr-1

2026-10-05 13:57Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-10-04 23:37Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-04 22:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-10-04 20:07Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write

2026-10-03 21:48Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-03 12:30Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write

2026-10-01 23:27Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-10-01 07:23Z — 1m 30s

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-10-01 07:17Z — 1m 30s

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, mesh.healthz.ewr-1

2026-10-01 06:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.healthz.ewr-1, mesh.healthz.ewr-1

2026-10-01 01:11Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.mono-1, io.healthz.ewr-1, io.login.ewr-1, io.pricing.ewr-1, io.root.ewr-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-09-30 20:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.healthz.ewr-1, io.pricing.ewr-1, mesh.healthz.ewr-1

2026-09-30 14:28Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-30 13:39Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-30 02:48Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-29 17:53Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-28 12:18Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.pricing.ewr-1, io.pricing.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-09-26 06:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-26 00:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.healthz.mono-1, io.login.mono-1

2026-09-25 18:24Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.docs.mono-1, io.login.mono-1, io.root.ewr-1

2026-09-25 14:49Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.mono-1, io.root.ewr-1, io.root.mono-1

2026-09-25 12:21Z — 30 seconds we did this on purpose

We shipped a release. The control plane restarted at 12:21:32 UTC for it, and 13 seconds later one check through one of our two hubs failed for a single 30-second cycle; we attribute it to that restart. Tunnels already up were unaffected. It is counted in full.

Failing: io.root.mono-1

2026-09-25 04:37Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-09-25 02:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-25 01:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-25 00:41Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-24 23:13Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-24 16:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-24 02:46Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-23 04:58Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-22 14:25Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.ewr-1, io.docs.ewr-1, io.docs.mono-1, io.login.ewr-1, io.root.mono-1

2026-09-22 07:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, mesh.healthz.ewr-1

2026-09-21 19:49Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, mesh.healthz.ewr-1

2026-09-21 18:01Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, mesh.healthz.ewr-1

2026-09-21 15:24Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.docs.ewr-1, io.login.mono-1

2026-09-21 03:34Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-20 17:35Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

2026-09-20 13:44Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 13:40Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 12:46Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.mono-1, io.docs.ewr-1, io.healthz.mono-1, io.login.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.mono-1

2026-09-20 12:20Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 12:11Z — 4m 30s

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 11:04Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 11:02Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: auth.login, auth.oidc, auth.token

2026-09-20 00:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: io.checkout.mono-1, io.docs.mono-1, io.healthz.mono-1, io.root.mono-1

2026-09-17 22:51Z — 1 minute

We have not established a cause for this one. It is counted in full regardless.

Failing: deep.write, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-09-17 16:22Z — 30 seconds we did this on purpose

We shipped a release. The control plane restarts during a deploy and the site returned errors for about thirty seconds. Tunnels already up were unaffected -- they do not run through the control plane -- but signing in and buying did not work, so it is counted.

Failing: io.checkout.ewr-1, io.checkout.mono-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.mono-1, io.root.ewr-1, mesh.healthz.ewr-1

2026-09-16 20:35Z — 1m 30s we did this on purpose

A deliberate failure drill. We stopped the control plane on the leader on purpose to find out how long recovery takes and whether our alarms fire. The site returned errors for about a minute and a half. We publish drills as downtime because that is what they are.

Failing: deep.write, io.checkout.ewr-1, io.checkout.mono-1, io.docs.ewr-1, io.docs.mono-1, io.healthz.ewr-1, io.healthz.mono-1, io.login.ewr-1, io.login.mono-1, io.root.ewr-1, io.root.mono-1, mesh.healthz.ewr-1, mesh.healthz.mono-1

2026-09-12 00:44Z — 30 seconds

Both hubs stopped answering our watchdog for a single 30-second check and were fine on the next one. The database write probe in the same cycle succeeded, so this was not the control plane falling over. We have not established the cause, and we are not going to invent one; it is counted as downtime.

2026-09-10 19:09Z — 1 minute we did this on purpose

We were hardening the sign-in service and restarted it. Sign-in was unavailable for about a minute; addresses and tunnels already up were unaffected, because they do not go through sign-in.

Failing: auth.login, auth.oidc, auth.token

tunnelnet.com

2026-09-27 06:15Z — 4h 55m

We have not established a cause for this one. It is counted in full regardless.

Failing: com.pricing

TunnelNet Monitoring

2026-10-21 09:00Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-10-19 02:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-16 16:39Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-10-16 01:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-12 22:28Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-12 15:21Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-12 03:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-10-12 02:40Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-09 23:56Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-09 00:02Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-10-06 22:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-06 21:20Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-06 11:45Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-06 01:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-05 14:36Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-10-05 13:57Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-10-04 23:37Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-04 22:26Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-03 21:48Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-01 23:27Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-01 07:24Z — 1 minute

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-10-01 07:17Z — 1 minute

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-10-01 01:11Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-30 20:38Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-09-30 14:28Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-30 13:39Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-30 02:48Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-29 17:53Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-28 12:18Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-09-25 18:24Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-25 14:49Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-25 04:37Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-25 02:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-25 01:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-25 00:41Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-24 23:13Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1, mon.api.mono-1

2026-09-24 16:52Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-24 02:46Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-23 04:58Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-22 14:25Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-22 07:10Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-09-21 19:49Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-09-21 18:01Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.ewr-1

2026-09-21 03:34Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

2026-09-20 17:35Z — 30 seconds

We have not established a cause for this one. It is counted in full regardless.

Failing: mon.api.mono-1

What we do not claim

There is no SLA today, and we are not going to imply one. An SLA is a promise with money attached, and a promise made on 43 days of measurement is a guess. We will offer one once we have six months of continuous measured operating history — that is 2027-02-21 at the earliest, and it is a date we will hold ourselves to on this page rather than in a sales conversation.

That date counts from 2026-08-21, not from the record below. We have watched this service from outside our network continuously since 2026-08-21; the finer 30-second record on this page begins 2026-09-10, when we replaced the original watchdog with the one that takes 25 checks every half minute. That six-month clock runs from the first, the numbers above come from the second, and we would rather show you both than quietly pick whichever suits the sentence.

We do not claim 99.9% uptime. The figure above is what was measured over the window stated beside it, and a week is not a year. Ask us again when this page has twelve months on it.

This page does not measure your address. The watchdog measures our service — sign-up, sign-in, the control plane, the site — from the internet. It cannot see inside your tunnel, and it is not telling you whether your machine was reachable. We probe every enrolled address separately, but the current population is overwhelmingly our own lab equipment being switched on and off, so a fleet-wide reachability percentage from it would be a number about our laboratory wearing the clothes of a number about your service. We are not publishing one until it means something. status.minaki.io shows that per-address probing for what it is.

Hub failover is not instant, and one case is not automatic at all. Measured on 2026-09-16: when a hub fails completely and withdraws its routes, a tunnel carrying traffic is reachable again in about 25 seconds — the client re-handshakes at about 16 seconds and routing catches up by 25. An idle tunnel took 37 seconds, and failing back when the hub returned took about 50. If a hub stays up and announcing but stops forwarding, nothing fails over and it needs us to intervene. We are building a health-gated route withdrawal to close that case; until it ships, this is what the product does.

How this is measured

One sample every 30 seconds from outside our network. A surface is counted DOWN for a whole 30-second cycle if any of its checks failed in that cycle. Time when the watchdog was not running is subtracted from the window and reported separately as not-measured — never counted as up.

Vantage	`meshd-quorum-do` — DigitalOcean, New York
Why there	Deliberately not on any machine it measures, and not on a control-plane node — a watcher that can be promoted to primary ends up watching itself.
Sample interval	30 seconds
Measuring since	2026-09-10

Time when the watchdog was not running is not counted as uptime. It is subtracted from the window and reported separately, because “we were not looking” and “it was working” are different facts and only one of them is evidence.

Some checks are deliberately excluded from the figures above, because they measure our own instruments rather than anything a customer buys — note this is not the same as the TunnelNet Monitoring figures above, which are a product and are counted: meta.peer – our dead-men watching each other — internal, deep.jobs – scheduled jobs still committing — internal freshness, deep.synthetics – our own lab fleet reporting — internal, deep.status – our status feed answering — monitoring, not the product, status.page – status.minaki.io itself — monitoring, not the product, canary – exists only while a drill is running. The raw record is at /uptime.json.

Record generated 2026-10-22 17:45Z — 2m 35s ago. Page written by tnet-uptime-render 1.0.0 on the web host, which is a different machine at a different provider from the control plane it reports on — so this page stays up when that does not. If it is ever unreachable, that is itself an answer.