Reliability
Know whether to fix or wait
Kyvera separates bot readiness, dashboard control-link health, Discord availability, and server configuration so administrators can act on the right problem.Read connection states
The bot is connected to Discord and the dashboard control API is responding.
The bot heartbeat is current, but live dashboard requests cannot reach the private control API.
Neither the control API nor a fresh database heartbeat reports a ready Discord connection.
The dashboard cannot obtain enough current data to confirm bot state.
Setup Diagnostics
- Checks whether Kyvera is still present in the server.
- Verifies the Discord permissions needed by configured modules.
- Detects deleted or inaccessible configured channels.
- Detects deleted, managed, or unreachable configured roles.
- Highlights issues before a deployment action fails.
- Can be refreshed after role, channel, or permission changes.
Status and history
Shows current health for the frontend, Discord API, Kyvera bot, and database without exposing infrastructure specifications.
Communicates investigating, identified, monitoring, and resolved platform events.
Records important module changes with the operator and timestamp for later review.
Explains product updates, behavioral changes, and staged feature rollouts.
Summarizes command success, feature activity, and Discord actions waiting for retry. Failed actions can be requeued after the underlying permission or resource issue is fixed.
A green platform status does not guarantee a specific server is configured correctly. Use Setup Diagnostics for server-specific failures.
The public status page is available even when you are signed out.