System Status
Real, per-component status — checked live and recorded every 5 minutes, starting from when this page shipped.
Live status
All systems operational
Checked 1m ago
API
The dashboard and booking API responding to requests.
Database
The primary database — bookings, calls, billing all read and write here.
Redis
Session, queue, and caching layer behind the API and voice platform.
Voice platform
Whether inbound calls can currently reach Ella — checked directly against Twilio's own account status, plus at least one voice worker being online.
Billing webhooks
Square's payment webhook endpoint — configuration and its database dependency.
Checked live on this page every 30 seconds, straight from the same checks that write the uptime history below — not a cached or hand-set status.
90-day uptime history
Tracking began 2026-08-17, recorded every 5 minutes. Days before that show as grey "no data" — we don't backfill or assume a day was healthy just because we weren't watching yet.
API
100.0% uptime over the last 6 days tracked
Database
100.0% uptime over the last 6 days tracked
Redis
100.0% uptime over the last 6 days tracked
Voice platform
97.4% uptime over the last 6 days tracked
Billing webhooks
100.0% uptime over the last 6 days tracked
Incident history
Voice platform — Twilio account authentication failing
11 Aug 2026, 3:20 pm → 17 Aug 2026, 10:39 pm
Twilio's Account API is rejecting our current TWILIO_AUTH_TOKEN (error 20003, "Authenticate", HTTP 401). Inbound calls are affected. First confirmed via the voice-health check's own commit (7acb9f0, 2026-08-11 05:20 UTC) — the earliest real evidence we have, not necessarily the exact moment the credential broke. Fix: rotate TWILIO_AUTH_TOKEN in Twilio Console and update the backend's environment. RESOLVED: TWILIO_AUTH_TOKEN rotated and the credential updated in production. Verified via the real voice-health check (/api/voice-health/public) returning healthy:true, detail:"active" immediately after api and all pipecat-voice workers were restarted with the new token.
No SLA, and we won't pretend otherwise
ZyncoAI doesn't currently offer a formal uptime SLA — our Terms don't promise one, and we'd rather this page tell you what's actually true than what sounds reassuring. What you see above is the real, unedited signal: live checks, honest history, and every incident we know about.
Subscribe to updates
We don't yet have automated status-update emails. For now, email us and we'll add you to the list directly.
support@zyncoai.com