System status
Operational — Live probes of public surfaces, latency and HTTP status, no cache. This page deliberately uses no cookies and no tracking.
Surfaces
| Surface | Status | HTTP | Latency | Endpoint |
|---|---|---|---|---|
| API Gateway | Operational | 200 | 24 ms | api.simosphereai.com/health |
| Workspace | Operational | 200 | 23 ms | workspace.simosphereai.com/ |
| App / Dashboard | Operational | 200 | 23 ms | app.simosphereai.com/ |
| Onboarding | Operational | 200 | 84 ms | onboarding.simosphereai.com/ |
| PostHog Analytics | Operational | 200 | 25 ms | posthog.simosphereai.com/decide/ |
| Plausible Analytics | Operational | 200 | 25 ms | plausible.simosphereai.com/ |
Note: Surfaces behind login (Workspace, App, Onboarding) correctly respond with HTTP 401/403 — this is rendered as "Degraded" but still means the surface is reachable.
More transparency
- Incident history — What we do when something breaks.
- Sub-processor list (GDPR Art. 28) — All sub-processors with location, data categories and DPA status.
- SLA, RPO & RTO — Uptime target, recovery point and recovery time disclosure.
- Compliance overview — GDPR, EU AI Act, ISO 27001, BSI C5, BFSG.
Report an incident
Spotted an issue that is not listed here? Please write to [email protected] or open a ticket at support.simosphereai.com.