Status
A plain view of OpenACAI public website, resource data, contact flow, API, app configuration, route manifest, and monitor status. This page is powered by the same public contract future mobile apps should read.
Current health
What the monitor is seeing.
Public-facing status contract state.
Short state for banners and future app clients.
Required components should be zero before app clients trust fresh data.
Optional diagnostics can fail without blocking public help paths.
Components
Public pieces this site depends on.
Each component includes what a visitor or app should do if it is not available.
Required
Public website
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: The public help site may be unavailable.
Fallback: Use last-known-good public resource data and retry the website.
Required
Public status page
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: Visitors may not be able to see current service health.
Fallback: Read the service-status JSON contract directly from openacai.ong.
Required
Resource data
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: Resource refresh may be unavailable.
Fallback: Keep the last validated resources.json and show its data age.
Required
Help planner
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: The start-here planner may be unavailable to apps.
Fallback: Open the public Start Here page and use the last known good planner contract.
Required
Contact flow
Status: Operational · HTTP: 200 · Cloudflare: DYNAMIC
Impact: Help request submission may require retrying later.
Fallback: Keep contact as a network web fallback and do not cache submissions.
Required
Public API
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: App startup metadata may be unavailable.
Fallback: Use last-known-good public contracts and retry the API.
Required
App configuration
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: Remote feature flags may be stale.
Fallback: Use last-known-good config and keep native-only features disabled.
Required
Route manifest
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: Native navigation metadata may be stale.
Fallback: Use public website links and avoid unsupported deep links.
Optional
Platform monitor
Status: Operational · HTTP: 200 · Cloudflare: HIT
Impact: Detailed diagnostics may be stale.
Fallback: Use this service status document for user-facing status.
How future apps should use this
- Refresh about every five minutes
- Use last-known-good public resource data when status is not operational
- Show a warning instead of hiding emergency or crisis links
- Keep native-only features disabled unless public contracts are healthy
Why contact is different
The contact page should not be edge-cached because it handles live form state and spam checks. Apps should open the web contact path rather than trying to cache or replay submissions.
Privacy boundary
The public status contract is safe to cache. It does not include private cases, uploaded files, help-seeker messages, staff emails, secrets, Cloudflare rule IDs, or origin IP addresses.
More technical views
Developers can also read platform health, mobile package, and API docs.