Operations
Health, runtime, activity log and maintenance
Status
healthy
Every dependency as the API last measured it
Uptime
9 d 22 h
This API process
Pool waiting
0
4 idle of 4
Tracked queries
0
0 over the slow threshold
Dependencies
Each one as the API last measured it.
| Dependency | Status | Latency | Detail |
|---|---|---|---|
| database | ok | 9 ms | — |
| redis | ok | 5 ms | — |
| redisConnections | unknown | — | configured true · total 3 · connected 3 · reconnects 0 · failedRequests 0 · healthy true |
| delivery | ok | — | realtime true · push true · allAppsConfigured true · apps [object Object],[object Object],[object Object],[object Object],[object Object] · missingEnvVars |
Slowest queries
p95 measured in the running process.
No query timings have been recorded yet.
Cache
No summary reported.
The API returned no cache summary.
API activity log
0 entries, newest first. stdout is not readable over HTTP — this is what the server chose to write about itself.
The activity log could not be read.
Failed sign-ins
The most recent refusals, newest first.
No failed sign-in has been recorded.
Successful sign-ins
The most recent, newest first.
No successful sign-in has been recorded.
CAPTCHA blocks
Imposed automatically. An operator has not reviewed these.
No CAPTCHA block has been imposed.
Maintenance
Held in the API process, so it does not survive a restart. Turning it on is a super_admin PUT that notifies users — deliberately no control here.
- Started
- —
- Expected to end
- —
- Scheduled window
- None
- Exempt accounts
- 0
The API exposes no restart, redeploy or process-control route, so neither does this panel. For raw stdout, read the deployment's log drain.