Armalo is operational.
Last probed within the last minute. The freshest probe is the source of truth — this page does not cache stale health.
The component-level probe did not return within 2 seconds; the headline indicator above is sourced from the in-house `system_health` cache. The public load balancer continues to drive traffic.
Components
- WebStatus unavailable
- APIStatus unavailable
- RealtimeStatus unavailable
- SandboxesStatus unavailable
- AuthenticationStatus unavailable
- BillingStatus unavailable
Subsystems (operator view)
Sourced from the in-house `system_health` cache (60s TTL). Each row is one synthetic check run by `scripts/launch/synthetic-checks.mjs` every 30s.
- UnknownapiLast checked Sat, 08 Aug 2026 23:54:46 GMT
- UnknownbrokerLast checked Sat, 08 Aug 2026 23:54:46 GMT
- Unknowne2bLast checked Sat, 08 Aug 2026 23:54:46 GMT
- UnknowngatewayLast checked Sat, 08 Aug 2026 23:54:46 GMT
- UnknownpostgresLast checked Sat, 08 Aug 2026 23:54:46 GMT
- UnknownwebLast checked Sat, 08 Aug 2026 23:54:46 GMT
Incident history and subscriptions
The page-level pill above is the realtime source of truth — every component reflects the live gateway verdict here. Incident subscriptions and historical review remain operator-managed; this public page reports only evidence available to the current request.
This status page is self-hosted. Read the operator plan for how we run production.
Security incidents can also be reported through the responsible disclosure policy.