Status
Check us yourself.
We don't publish a hosted status page yet, and we're not going to paint a green dot on this one — a page served by the system it reports on can only ever tell you it's up. Here is what to check instead, and what happens when something breaks.
Check it directly
Three surfaces, in the order worth trying. Each one is live right now.
Returns JSON and HTTP 200 when the app is serving and the database answers a query; HTTP 503 when the database is unreachable. It is deliberately unauthenticated so an external uptime monitor can poll it — see below for where that stands.
The invitee-facing surface — a public booking link. If it loads and shows times, the scheduling engine and the database are both working.
Sign-in goes through Google. If sign-in specifically is failing while booking pages load, check Google Workspace status below before reporting it.
What we monitor
Being precise here, because this is the one claim on the page you cannot check: the application reports its own errors — failed bookings, calendar-sync failures, billing webhook errors — to an error-tracking service, and the endpoints above exist to be polled from outside our infrastructure. The external uptime monitor and the alert rules on the paths that touch money or a confirmed booking are configured at launch, not before it. Until they are, a failure reaches us when someone tells us, and you should assume exactly that. We are not publishing uptime numbers either, because we have not been measuring long enough for a number to mean anything honest.
Upstream providers
Most outages that affect you start at one of these. Their status pages are authoritative.
During an incident
Our commitment: if an incident affects bookings, we email the hosts whose links were impacted rather than waiting for them to come looking for a status page, and we say what happened. Maintenance that requires downtime gets an email in advance. We are a young product and have not had to do either yet — this is the policy we intend to be held to, not a track record.
A hosted status page on a separate provider — so it stays up when we don't, with subscribable incident updates — is planned and will be linked from here and from the footer when it exists. See also our security and privacy page.
Something broken?
Tell us what you were doing and what you saw. Include the booking link if it involves one — that gets us to the right logs immediately.
support@neos.network