DocsHelp
Vallit status
Whether every part of Vallit works right now, and what happens when one does not.
In short
- status.vallit.net shows whether every part of Vallit is working right now. It is public, so you can read it without an account.
- Every part is checked once a minute from our servers. The whole app is also checked every five minutes from outside them, so a Vallit that is down entirely is noticed too.
- Open it from Vallit status in the account menu at the foot of the sidebar, or from Status in the footer of vallit.net.
What the page shows
The line at the top sums up every part: Everything is running, Some parts have trouble or Something is not working. Checks are late means the page has not heard from the checks for more than three minutes, so it does not vouch for an old answer.
Below it, the parts are grouped: Website, App, Accounts and sign-in, Checks and monitoring, Data, Email, payments and GitHub, and Security. Each part carries one word.
| What you see | What it means |
|---|---|
| Running | The part works. A single slow answer or a single failed check does not change this word. |
| Degraded | The part answers, but slowly or with some errors, and it did so three checks in a row. A service we hand work to also shows this when it reports trouble on its own status page. |
| Down | The part keeps failing its check: two checks in a row, three for the services under Email, payments and GitHub. Some parts, such as certificates and background jobs, show it after one failed check. |
| Not checked | We could not look this minute, or a background job has not run yet since the record began. A job that runs once a day shows this until its first run. It does not count as trouble. |
Each part has its own speed limit, set from how fast it answered over several days. Only the time the service takes to answer counts, not the time to set up the connection.
The i next to a part says what the part does for you and what its last check found. When that check was slow or failed but has not repeated yet, it says so, for example “One slow answer (2.5 s); watching” or One check failed; looking again.
Each group has a bar for the last ninety days, one line a day. Point at a day, or tap it on a phone, to read how much of that day the group was working. The bars count what the page showed, so a single slow or failed check does not mark a day. A grey day is a day nobody looked: the record starts on 30 September 2026.
When something goes wrong
A part that shows Down opens an incident: after two failed checks in a row, one minute apart, or three for the services under Email, payments and GitHub. A part that stays Degraded for ten minutes opens one too. It appears under Right now with the time it started.
Our team is told at once, and an AI agent starts looking into the cause. It proposes a fix, and a person at Vallit reviews that fix before anything changes. While this is under way, the incident reads We are working on it now.
When the part passes two checks in a row again, the incident closes. It moves to Past incidents with how long it lasted.
Use it in your own tools
https://status.vallit.net/api/status returns the same information as JSON: the overall state, the state of each part and the open incidents. It needs no key. It never includes the internal detail of a check, only what the page shows.
Related
- Troubleshooting lists the error messages in the app and what to do about each.
- Updates and versions says what changed in each release.
- Your profile shows where the account menu is.