Is the bot up?
not yetThis process has not logged in yet — normal for a host that sleeps and has just woken up.
gateway: not connected
Four questions, four answers
Being up is not the same as being configured
The bot's health line deliberately keeps these apart. A process can be running with nobody able to sign in; the bot can be connected while the public site publishes the wrong directory; the service can be up today and have been down for two hours last Tuesday. Folding them into one word is how a monitor that pages on "is it healthy" never fires for any of the three.
Is it configured?
read liveHow many settings would stop something working if left absent. This one has to be read from the host itself — the machine that built this page has a different environment.
the live read fills this in
Is the public site publishing safely?
unknownNot checked yet in this process.
no check recorded yet
Has it been reliable?
unconfiguredNo monitor reading to show. The watcher is configured in the host's environment, not here, so this says nothing about whether the bot is up.
no reading recorded yet
Configuration
53 settings, read from the host itself
Counts only, and no names. This page is public, and "this deployment has no sign-in secret" is not a sentence to hand a stranger — so the names live behind the console's sign-in, and what is published here is how many are missing and how much each one would cost you. A missing essential is a feature that cannot work; a missing tuning value is a default you may be perfectly happy with.
| What it costs you | Missing | Present | Of |
|---|---|---|---|
| Essential A feature cannot work at all without it. | — | — | 1 |
| Security Something is reachable that should not be. | — | — | 4 |
| Capability A feature works, but with less than it could do. | — | — | 13 |
| Tuning A default is in use. Often fine. | — | — | 31 |
| Host The platform provides it; absent means the host is not set up. | — | — | 4 |
What has been counted
Four windows, and the same counting code behind all four
"Last 7 days" means today and the six days before it — the same seven
days /activity and the weekly digest mean, because it is
the same arithmetic. A figure that was never read is shown as a dash
rather than as a zero: a sleeping host has no gateway to ask, and a
confident 0 servers reads as a bot nobody uses instead of as a
process that has not woken up.
read just now
| Window | Messages | Voice time | Channels | People seen |
|---|---|---|---|---|
| Today 1 days | — | — | — | — |
| Last 7 days 7 days | — | — | — | — |
| Last 30 days 30 days | — | — | — | — |
| All time everything kept | — | — | — | — |
Ask it yourself
Every reading on this page has a URL
Nothing here is computed for the page alone. These are the endpoints the hub itself reads, they are all GETs, and each one is safe to hand to a monitor or open in a tab.
| Endpoint | What it answers | Sign-in | |
|---|---|---|---|
/api/status |
Every figure on this hub, merged into one small payload. | public | |
/health |
Four separate claims: up, configured, publishing safely, reliable. | public | |
/api/figures |
Servers, members, and four counted windows. | public | |
/api/uptime |
The monitors themselves — names and addresses. | signed in | |
/api/config |
Every setting, present or absent, by name. | signed in | |
/api/command-scope |
What Discord actually holds for one server, beside its switches. | signed in |