System status
All systems operational
Health is checked every 60 seconds across all regions. Recommender-mode AI is non-blocking, so assistant slowdowns never affect clinical writes.
99.98%
Uptime, last 90 days
41m
Longest incident, last 90 days
3
Incidents, last 90 days
Services
API gateway
REST routing & request aggregation
Realtime
Supabase channels & read-model fan-out
Read models
Encounter journey, queues & caches
AI platform
Assistant, coworkers & inference fabric
Interoperability
FHIR R4 · HL7v2 MLLP · DICOM MWL
Filestore
Uploads, documents & IPFS
Messaging
Socket.IO, email, SMS & push
Authentication
JWT, login, RBAC & bio-attestation
Regions
Each market pack runs in its own data-residency region.
United States
us-east-1
UK / Europe
eu-west-2
Japan
ap-northeast-1
China
cn-north-1
Southeast Asia
ap-southeast-1
Australia
ap-southeast-2
Past incidents
Elevated AI assistant latency in ap-southeast-1
Inference queue depth on the shared Ollama node caused assistant responses to slow for ~40 minutes. Traffic was shed to the server tier and capacity was added. No clinical writes were affected — recommender outputs are non-blocking by design.
Scheduled maintenance — Filestore IPFS pinning
Planned migration of the IPFS pin set to expanded storage. Uploads were briefly queued and delivered once the window closed. Announced 72 hours in advance.
Realtime reconnect storm after a Supabase failover
A managed Postgres failover triggered a reconnect storm on realtime channels. Read models stayed consistent; clients recovered automatically with backoff. We tuned reconnection jitter to prevent recurrence.