Uptime target
99.9% monthly target — a goal, not a contractual commitment. Any service level belongs in a signed order form.
Status
What is working right now, the commitments we publish, and every incident we have on record. The two system checks run when this page loads.
Sign-in, publishing, the customer workspace, the admin console and the document viewer.
Crawling, OCR, transcript extraction, translations and the weekly rescan of customer websites.
Every incident we post appears here with its severity and how long it lasted, including the ones we resolved quickly.
99.9% monthly target — a goal, not a contractual commitment. Any service level belongs in a signed order form.
Monday to Friday, 08:00 to 17:00 Arizona time (MST, no daylight saving)
Daily encrypted database export, checksum-verified, on a tiered retention schedule. Document files are not included in this export.
Planned maintenance is announced at least 3 business days ahead.
| Severity | First response |
|---|---|
| Severity 1 — publishing unavailable | 1 business hour during support hours |
| Severity 2 — degraded processing | 1 business day |
| Severity 3 — question or request | 3 business days |
These are targets, not a contractual commitment. A service level, if one is agreed, is set in a signed order form.
Two checks run each time you load this page: a live database read for the application, and the ingest worker's heartbeat for document processing. Commitments and response targets are written policy reviewed with the rest of our published commitments, and incidents are posted from our operations console as soon as we confirm them. If you see something this page does not reflect, tell us.