Operations

Service status

Operational health for Qortora deployments. Service commitments are governed by the applicable deployment or customer agreement. This page is intentionally calm during incidents: facts first, no speculative root-cause language until confirmed.

Search activity

Expectations

• Best-effort public demo unless a written SLA applies to your tier.
• Search path should remain available even when crawl or optional AI backends are degraded.
• Index freshness depends on crawl lag and corpus load; thin coverage is disclosed in the SERP, not hidden behind a silent third-party skin.

Incident tone & runbook (operators)

1. Confirm blast radius via GET /api/status, process logs, and reverse-proxy health — not social media first drafts.
2. Prefer accurate “degraded / investigating” language over premature root cause.
3. Check data/logs/qortora.log and data/logs/qortora-crash.log; verify disk, Speedb data dir, and TLS termination.
4. If search is up but crawl is stuck, say so explicitly; users care about query answers first.
5. After recovery: short postmortem (timeline, impact, fix, follow-up) for internal or customer channels as required.

See docs/HOSTING.md for production checklist, tiers sketch, and log paths.

Raw /api/status

…