Service Status
Arximus status reporting should show the health of the cloud API, dashboard, event ingestion, backup orchestration, storage, restore services, alert delivery, policy distribution, and Edge WAF infrastructure.
Availability
When Arximus protects your sites, you need to know whether policies are syncing, events are ingesting, backups are running, alerts are delivering, restore services are available, and Edge WAF traffic is being handled normally.
The status page should become a public operational surface once production services launch.
Clear incident updates
Arximus status reporting should show the health of the cloud API, dashboard, event ingestion, backup orchestration, storage, restore services, alert delivery, policy distribution, and Edge WAF infrastructure.
Component health
A useful status page separates Arximus Cloud, plugin API, policy distribution, decision API, event ingestion, backup storage, restore jobs, alert delivery, billing, dashboard, and Edge WAF regions.
Components
Customers need component-level visibility, not one vague status light.
01
Enrollment, entitlements, policy sync, decision API, event upload, dashboard, and operator functions.
02
Upload intents, chunk receipt, storage, manifest verification, backup inventory, and restore planning.
03
Email, webhook, dashboard, and external alert delivery routes.
04
Regional edge availability, origin proxying, policy distribution, challenge service, and edge log ingestion.
Production status
This page can be connected to live monitoring when services launch.
Show recent availability for key Arximus services.
Publish past and current operational incidents with customer impact.
Announce scheduled work that may affect policy sync, dashboard access, or backup operations.
Let customers subscribe to operational updates for relevant components.