Uptime & Reliability
The Status Page tells you what's currently known about Nexa's services. This page explains what that actually means in practice.
What the status page is
It's a visibility tool, not a guarantee. When something goes wrong — NexaBot stops responding, Nexa Assistant errors out, the Dashboard won't load — the status page is where that gets reflected, usually as soon as it's identified.
No formal uptime SLA
Nexa doesn't currently publish a formal uptime percentage or service-level agreement. If uptime guarantees matter for your use case, that's worth raising through Support & Contact so it can be considered.
What tends to cause downtime
Realistically, most disruptions fall into a few categories:
- Discord API issues — NexaBot depends on Discord's own API being healthy; a Discord-side outage looks like a NexaBot outage even when nothing on Nexa's end is wrong
- Deploys — pushing an update can occasionally cause a brief blip while the new version comes online
- Upstream provider issues — Nexa Assistant depends on external model providers; if one of those has an outage, responses may slow down or fail until it recovers
What to do if something seems down
- Check the Status Page first — if it's a known issue, there's nothing more to do but wait
- If the status page shows everything healthy but something still isn't working for you, it's likely specific to your setup — see Permissions Troubleshooting for NexaBot, or Errors for Nexa Assistant
- If neither explains it, reach out — a report that isn't already reflected on the status page is genuinely useful
Why this page exists
Being upfront about what "status" does and doesn't promise is better than implying a level of reliability that isn't actually being tracked or committed to yet.