Tenvo service status
Reachability of the services your client connects to. Each row is checked on every page load — no caching, no stale dashboards. The marketing site and authentication are probed directly; the rendezvous and relay rows only reflect DNS/website reachability (no public health endpoint), so a green light there means the hosts are addressable, not that a live session is succeeding.
Checked just now (server-side, every request).
Marketing site
349mstenvoai.com (this page)
Authentication
39msSupabase auth + tier limits + sessions audit
Rendezvous DNS / reachability
386msid.tenvoai.com (peer ID lookup, TCP 21115). No public health endpoint — this row reflects DNS/website reachability for the shared DNS zone, not a live probe of the rendezvous port.
Relay DNS / reachability
481msrelay.tenvoai.com (fallback when P2P fails, TCP 21117). No public health endpoint — this row reflects DNS/website reachability for the shared DNS zone, not a live probe of the relay port.
HTTP services (marketing site, authentication) are checked with a HEAD request and a 5-second timeout. The TCP services (hbbs / hbbr on ports 21115 / 21117) have no public health endpoint, so we cannot probe them directly. Their rows instead reflect DNS/website reachability for the shared DNS zone — a useful "are the hosts addressable?" signal, but it will not turn red if the rendezvous or relay daemon is down while the website stays up. If you suspect an actual connection outage, please email support@tenvoai.comand we'll investigate immediately.
We do not run a paid status-page service yet. Historical uptime graphs and subscribe-to-incidents will be added once there are enough incidents worth showing — until then, this live check tells you everything you need.