Nothing has been reported — a different claim from everything confirmed working.
This page tells you one specific thing: whether a problem has been reported against any part of Dohos, right now. It does not tell you that every part has just been checked and found healthy, because no system does that continuous checking today — and this page is built not to imply otherwise.
Two different claims — this page makes the narrower one.
A status page can say one of two things. The first is a positive claim: a system watches every part of the product continuously, and this page reflects what that system just confirmed. The second, narrower claim is honest instead: nothing has come in — from the team, from a restaurant, from a caller — reporting that something is broken. This page makes the second claim, because the first would need a monitoring system that doesn't exist to stand behind it.
The reports this page draws from are written by the people actually handling whatever is happening, not generated by an automated check. That's a real, legitimate way to run a status page, stated here plainly rather than dressed up as more automatic than it is.
What doesn't appear anywhere on this page, on purpose: a percentage of time the product has stayed available, a stated detection speed, or a specific monitoring method and how often it runs. The availability commitment covers what a future measurement is designed to cover, and exactly which figures aren't set today.
Five real, currently running systems — nothing more, nothing hypothetical.
Each row gets the same honest, either-or reading: nothing reported, or something reported and being worked. There's no separate percentage or score per system, and a capability that hasn't shipped doesn't get a row here just because a longer list would look more thorough — five is the honest count of what's actually running.
The fuller record behind this one-line reading — including exactly what gets written down when something is confirmed — is at incident history.
How do I know this page is accurate?
It reflects exactly what’s been reported through it, no more and no less. Incident history is the same claim in its complete, dated form.
What if something breaks and this page still says nothing's wrong?
There’s a real gap between something going wrong and it being confirmed and written up here, because that confirmation is done by people, not an automatic sensor. What’s real regardless: if the voice line can’t take a call, it doesn’t just go to silence — it forwards to a number the restaurant has already set.
Does an empty page mean nothing has ever gone wrong?
No — it means an entry gets written here when something is confirmed, not filtered out for looking bad. There’s no separate, quieter channel where a real problem gets handled without reaching this page.
Where do I go if I think something's wrong right now?
Support is the same channel for this as for anything else. Flagging a suspected problem there is what actually starts the process that would turn into an entry here, if it’s real.
Open the line.
Tell us about your restaurant. We load your menu, you place a call, and you hear it answered yourself.