Where to Check Whether Levlix Is Working
If commands stop responding, the first question is whether the problem is your server, Discord, or us. That question now has a page: levlix.io/status.
What the Page Reports
Levlix is not a single service, so a plain "up or down" would hide more than it shows. The page breaks health down by the three components a request actually passes through:
- Bot gateway. The websocket connection to Discord, reported with its current latency. If this degrades, slash commands are slow or silent.
- Database. The primary store for points, characters, cases and configuration, reported with query latency.
- Cache. The in-memory store behind sessions and cross-process events, reported with its own latency.
Alongside those, the page tracks Discord's own availability, because a Discord incident looks identical to a Levlix incident from inside a server.
The 90-Day History
Below the live components sits a 90-day grid, one marker per day, with an overall figure beside it. It answers the question a live indicator cannot: is this a bad minute or a bad month.
Under that, Past Incidents lists what actually went wrong and when. The section only appears when there is something to report, so an empty page is the honest kind of empty.
What We Do Not Promise
The page shows a 90-day uptime figure, and labels it Overall SLA. Read that as what it is: a measurement of the period behind it, not a commitment about the period ahead. Levlix offers no availability guarantee, and the terms of service do not contain one. The bot is free to add and free to run, and we publish the record so you can judge it yourself rather than take a promise on trust.
The page is public and needs no login, so you can link it in your own server when members ask.