Naven
The numbers
| Status checks, 16 September 2026 to 16 October 2026 | 83,582 across 11 parts of Naven |
|---|---|
| Checks that failed | 1 (Naven AI, on one day) |
| Server requests, 9 October 2026 to 16 October 2026 | 154,221 |
| … that ended in a server error | 271 (0.18%) |
| … ended because the visitor had gone | 14,267: a closed tab, a phone asleep, a live connection closing. Not a server failure, and not counted as one |
| Median server processing per successful request | 3.7 ms of CPU |
The checks are the ones the status page runs and shows, with ninety days of history: signing in, sending and loading messages, screening, pictures and voice notes, calls, Naven AI, channels, notifications, email and the parent controls. The request figures are Cloudflare's own count of every request to the server that runs Naven.
What happens when part of Naven fails
- Screening fails closed. If the screening models cannot be reached, the rule-based layer that runs on every message still decides. A message is never let through unscreened because a provider is down.
- No connection. Naven opens and shows what it last loaded — conversations, messages, the pictures and voice notes already opened, the channel list — and a message being sent is shown in the conversation, marked as sending, until the server accepts it.
- Calls step down, not off. A call between two adults usually goes straight between their devices; every other call goes through Naven's own call server, and only when that cannot carry it through Cloudflare's relay or, last, Agora.
- Where Google is blocked. Naven's connections to Google's database go through navenapp.com, so the app works on networks that block Google. Google sign-in itself cannot work there; an emailed code or a passkey can.
- Free allowances with hard limits. Naven runs on the free tiers of its providers. Where an allowance has a cap, the feature stops at the cap rather than running up a bill.
What went wrong before, and what changed
- 27 September 2026. The database's free daily read allowance ran out, and much of the app returned errors until the allowance reset. Presence and other frequent reads were moved off that database, and the busiest paths no longer read from it at all.
- Until 10 October 2026. Some requests timed out, and about one run in five of the five-minute scheduled job was stopped by the free plan's processing limit. The job was split into one task per run, and signed-in requests now make one round of lookups instead of five. Measured over the same nine hours a day apart: median server time fell from 277 ms to 126 ms, and runs stopped for processing from 4 to 0.
What Naven does not promise
There is no uptime guarantee and no service-level agreement. Naven is built and run by one independent developer, and its terms make no promise of availability. What it does instead is measure itself in public: the status page is checked rather than written, and this page is re-measured with dates attached.
Questions
Is Naven down right now?
The status page shows the result of the most recent check of every part, made about every five minutes.
Why do some assistants say Naven is unreliable?
Usually because they have little to go on: Naven is new, and its name is close to other companies' — Navan, a travel and expense company with its own reviews, and Naven Network, a payments company with a cryptocurrency token. Reviews of those are not about Naven. The figures on this page are.