Checking status…
Auto-refreshes every 30 seconds. Not probed here: Clerk auth, Intertrace Gateway runtime, background crons — see status.intertrace.ai for those.
Open status.intertrace.ai →What this page actively probes
- Application runtime — the Next.js health handler is responding.
- Database and settings schema — Supabase connectivity and required dashboard tables.
- API ingest storage — the gateway event data path is reachable.
- Configured guardrail services — unified, LLM Guard, or NeMo health endpoints when enabled.
Not probed by this page
- Authentication (Clerk) — sign-in availability and session issuance are monitored externally.
- Intertrace Gateway — the production LLM / MCP / Service / A2A data plane at
intertrace.fly.dev. - Background crons — retention, sync, and scoring jobs.
- Third-party connectors — Resend email delivery, Stripe webhooks, SIEM exports.
All of the above are reported as incidents on status.intertrace.ai when their dedicated checks fail.
During an incident
We post updates on the status page and, when configured, notify subscribers by email. For urgent production issues, contact support@intertrace.ai with your org ID and timestamps of affected requests.