QubaxQubax AI
Get started

System Status

Real-time uptime and performance for Qubax AI services.

How Qubax monitors API health

This page shows the live health of the Qubax AI API at api.qubax.ai: the API gateway, the database and the cache layer. A health probe runs every 60 seconds and records whether each component responded and how long it took. Uptime is the share of probes that succeeded over the last hour, 24 hours and 90 days.

Status covers the Qubax platform itself. Individual models are served by many independent compute providers; if one provider for a model fails, the router retries the request on the next-cheapest healthy provider, so a single provider outage usually does not show up as an error for your request.

If you see errors that this page does not explain, check the HTTP status code first: 401 means the API key is wrong or revoked, 402 means the account balance is too low, 429 means you hit a rate limit, and 5xx means a temporary upstream problem that is safe to retry with backoff.

Frequently asked questions

Is the Qubax API down right now?
The banner at the top of this page shows the current state, refreshed every 30 seconds. "All systems operational" means the API, database and cache all passed their last health check.
What uptime does Qubax AI have?
Uptime is measured from 60-second health probes and shown above for the last hour, 24 hours and 90 days. The 90-day figure is the best indicator of long-term reliability.
What should I do when a request fails?
Retry 429 and 5xx responses with exponential backoff (for example 1s, 2s, 4s). The OpenAI SDKs do this automatically. 401 and 402 errors will not succeed on retry: fix the key or top up the balance.
Where can I report an incident?
Message the Qubax team on Telegram at t.me/Qubax with the time, model ID and the error message you received.