Status
Measured, or not said.
This page asks the live API how it is doing — from your browser, the moment you open it — and prints what came back. There is no hardcoded green light anywhere on it: a green light that does not depend on the answer would be a lie the first time it mattered.
Checking…
Your browser is asking
api.answermend.com/health right now.
What the API reported
| Part | State | What that means |
|---|
The three states this page can show
reachable, healthy
The API answered from this browser and nothing it reported about itself is failing. Parts that are switched off or not yet measured are listed as exactly that, because “not configured” wearing a green light is how a status page starts lying.
reachable, with problems
The API answered, and something in the answer is wrong — an engine failing its calls, the day’s engine budget spent, the service reporting a state other than ok. The band above names each problem rather than averaging them into a colour.
could not reach — unmeasured
The request from your browser did not complete. That is the state everyone rounds to “down”, and this page refuses to: an unanswered request can mean the API is unreachable, or that your own network, an extension or a firewall stopped the call. Unmeasured is its own answer.
Why there is no uptime percentage here
Status pages traditionally end in a number like 99.9%. This one does not, because that number has to be measured by something that watched the service over a long window, and no such history has been recorded here yet. Publishing a percentage anyway would mean inventing it — the exact thing this product exists to refuse. If an uptime figure ever appears on this page, it will arrive with the window it was measured over and the thing that measured it.
The same honesty runs the other way: the terms promise no uptime figure either. What you get is this page, which reads the real state, and the build log, which records what broke and what was done about it.