System status
All systems operational.
Live service health, updated every 60 seconds. Subscribe to incident notifications at status@tryorbell.com.
| Service | Region | Status | 90-day uptime |
|---|---|---|---|
| Call answering | Global | Operational | 99.99% |
| Voice processing | US-West | Operational | 99.98% |
| Voice processing | EU-Central | Operational | 99.94% |
| Voice processing | AP-Southeast | Operational | 99.97% |
| Calendar sync | Global | Operational | 99.92% |
| Dashboard & API | Global | Operational | 99.99% |
| SMS & notifications | Global | Operational | 99.96% |
Incident history
Everything that went wrong this year.
Elevated latency on EU voice processing
For 34 minutes, first-response times in the EU region averaged 780ms against a 420ms baseline. Cause: a failed capacity rollout. No calls were dropped. Rollback completed at 14:22 UTC.
34 min
Calendar sync delays (Google)
Bookings were written correctly but took up to 9 minutes to appear in Google Calendar, caused by an upstream rate limit. Confirmations to callers were unaffected. Backlog cleared by 19:40 UTC.
2 h 10 min
Dashboard sign-in failures
A certificate rotation broke SSO sign-in for accounts using Okta. Call answering was never affected. Fixed in 41 minutes; affected accounts were emailed the same day.
41 min