Checking

Checking system status…

This public board runs sanitized reachability checks for Aptoria's API and database. It is a current snapshot, not a provider-status claim or historical uptime score.
Probing services…
Refresh now
Operational
Reachable and healthy
Degraded
Up, but not fully configured
Down
Failing its health probe
Not configured
Credentials absent here
How this page works
Each row is returned by the anonymous health endpoint. The public response is deliberately limited to API and database reachability and does not expose integration credentials, tenant data, payment-provider health, email-provider health, or AI-provider health.
What is monitored
The board checks whether Aptoria's public API can respond and whether the application can reach its primary database. A successful check means those specific paths answered at the displayed time. It does not prove that every workflow, third-party provider, background job, or customer-specific integration is available. Payment, email, document-signing, screening, and AI providers have their own operating boundaries and may be unavailable even when Aptoria's core checks are healthy.
Updates, incidents, and support
Checks refresh in the browser every 30 seconds while this page is visible. Aptoria does not publish a historical uptime percentage from these reachability probes. If a check reports an incident, retry after a short interval and preserve the affected workflow's record before taking another action. For an issue that persists, email support@aptoria.ai with the time, affected workflow, and any receipt or error identifier; do not include passwords, payment credentials, or sensitive tenant documents.