Website
Public site and authenticated workspace
TAVONEL service status
The first group below is TAVONEL’s live configuration and activation state, read 01 November 2026 at 00:15 KST when this page rendered. “Configured” means the component is configured and its gate is open; it does not mean a request recently succeeded. Scheduled checks report request outcomes separately further down. Report an outage you are seeing rather than waiting for it to appear here.
Configuration and activation state
Authentication
Google OAuth through the dedicated Supabase project
Document pipeline
Quarantine, CDR and GPU OCR candidate processing
Billing
Paddle live checkout configured; checkout is closed and no plan can be bought
Export
Signed portable knowledge packages
Scheduled dependency checks
Request checks here run on a schedule without customer data and report what came back. Billing is a configuration-only check; it sends no request through a payment flow. A row marked “not probed” is neither a pass nor a failure: nothing was sent, and the reason is given.
Last check that passed: 01 November 2026 at 00:10 KST. Most recent check of any outcome: 01 November 2026 at 00:10 KST (passed). 0 of the last 20 stored runs did not pass.
Document sanitizer
answered in 418 ms
GPU OCR
not probed: a health request would cold-start a GPU worker
Compiler core
answered in 90 ms
Object storage
answered in 354 ms
Database
answered in 78 ms
Billing
configuration only; no request is sent through it
Full pipeline check: Not covered. The scheduled checks do not carry a document through the full pipeline, so nothing here reports on sanitization or document reading.
Incident history
No incident has been recorded since 1 September 2026, the first release recorded in the changelog. When one occurs it is published here with what happened, what it affected and what changed afterwards, and it stays published. What is published is a customer-facing record: never a log location, a request id, a digest or another customer’s name.
If this page is unavailable, report service impact to support@tavonel.com.
Getting told without coming back
Releases and the changes that come with them are published on the changelog, which has an Atom feed any reader can subscribe to. For an incident affecting your workspace, email support@tavonel.com for direct updates.
Incident contact
Report service impact to support@tavonel.com and security issues to security@tavonel.com. Do not include document contents in email.
Email to support@tavonel.com is acknowledged within 1 business day (KST). That is an acknowledgement target and not a resolution time: no resolution time is committed, and security reports to security@tavonel.com are read first rather than queued behind product questions.