Waiting for the first reportsUpdated 07:04 PM UTC

Network status

Share of successful connections per protocol and network over the last 6 hours, from real user reports, unsmoothed.

The network is being deployed. Numbers appear here the moment the first servers report — we don't show figures we haven't measured.

  • 0attempts
  • 0servers online
  • 0protocols
online offlineMarkers are illustrative until the first servers report.

Last 48 hours

One bar per hour. Hover a bar for its numbers.

48h agonow

No hour has five reports yet — the bars fill in as devices connect.

  • 97% and above
  • 90–97%
  • below 90%
  • not enough data

Servers 0

No servers registered yet.

Protocols

Not enough data yet: a protocol appears here once it has five measured attempts.

How we measure

Nothing smoothed, nothing hidden: this page shows exactly what devices reported.

  1. 1

    A device connects

    Our app or any client tries a protocol on a server.

  2. 2

    It sends a short report

    Server, protocol, network type, outcome and connect time. Never an IP address, traffic or DNS.

    The full request body
    { "device_id": "dev_…", "node_id": "node_…", "protocol": "wg", "network": "wifi", "outcome": "ok", "latency_ms": 184 }

    The server stores it with your account and the time, so a day without a working connection can be credited back. Individual reports are never published — only the sums on this page.

  3. 3

    We publish the sum

    The success share over a rolling six hours, failures included — exactly what you see here.

  • No IP addresses
  • No traffic
  • No DNS queries
  • No browsing history