Status
These checks run when you load this page and again every thirty seconds. They are the same checks we watch, not a status board someone remembers to update.
Checking…
What each check means
Database is a real read, not a ping — a database that accepts connections but cannot answer is the failure that matters, and only a query finds it. If this is down, the dashboard and your widget are both affected.
Answer generation is the model provider. If it is down, your representative stops answering; the widget says so rather than guessing.
Semantic retrieval degrading is not an outage. Answers fall back to keyword matching — less precise, still grounded in your pages.
Email and billing affect password resets and checkout. Neither stops an installed widget from answering.
Reporting something we have not caught
If this page says everything is fine and your experience says otherwise, that is worth an email — it usually means a failure mode we are not checking for. Write to hello@rubyrep.com or use the contact form.
Uptime commitments
We do not publish an uptime figure, because a number we calculate about ourselves is worth very little. There is no contractual uptime guarantee on the standard plans — see the Terms.