Status
Operational status and issue reporting.
This page is the customer-facing status entry point. It links the exposed health surfaces and explains what to send when reporting worker queue, output quality, billing, API, or login issues.
Status model
BoringKit avoids fake uptime claims on static pages. Live health, readiness, and version endpoints are exposed separately; queue, payment, and processor issues should be verified with account/job context.
Web app
Public pages, account console, workspace, pricing, and tool pages.
API
Tool metadata, auth callbacks, jobs, credits, billing, API keys, and download intents.
Readiness
Whether the web runtime is ready to serve customer traffic.
Version
Current deployed web/runtime version information when exposed.
Worker or queue issue
Send the tool name, job ID, status, created time, file type, expected output, and the smallest safe description of the failure.
Output quality issue
Mention whether the problem is layout, font, page count, text extraction, image quality, codec, duration, or download expiry.
Billing or account issue
Include account email, plan, checkout/reference ID if visible, and what changed. Do not send full card numbers or secrets.
Need help now?
Use the contact form for production issues. Include only non-sensitive context. If a job is active, keep the workspace row open until support has enough job metadata to investigate.