DocsBolt status
Current health of the API, database, AI generators and every file tool. Checked automatically; this page refreshes every minute.
Components
Past incidents (30 days)
Incident history is unavailable while the API is unreachable.
How this page decides
Core components are probed directly every minute: a database ping, a storage read, a credentials check against the AI provider, and a version call to the document engine. Tools are judged on their own results from the last 30 minutes — failures on our side only; a wrong password or a missing second file is not an outage. Three or more failures at a 50 % failure rate is a major outage, two at 25 % a partial outage, a single failure shows as degraded. A slow cold start of the document engine also shows as degraded rather than as an outage.
A core component has to fail two checks in a row before it counts as an outage — a single failed check shows as degraded. Incidents open at partial outage or worse and close automatically once the component has been clean for three minutes; the people who run DocsBolt are e-mailed when one opens and when it resolves. If the API itself stops answering, an external monitor raises the alert — this page cannot rely on the API to report its own absence.