Reliability & uptime
A phone system that drops customer calls is worth less than nothing. DialPhone targets 99.999% uptime across every product — voice, video meetings, SMS, contact center — backed by service credits when we miss.
Reliability metrics
- Target uptime
- 99.999%
- RTO (recovery time)
- <15 min
- RPO (data loss window)
- <5 min
- Active data centers
- 4 US + 2 EU
- Service-credit backed SLA
- Yes
- Public status page
- status.dialphone.com
Architecture
- ✓ Active-active across 4 US regions and 2 EU regions — no cold failovers
- ✓ Carrier-diverse PSTN peering — no single-carrier dependency
- ✓ Geo-replicated databases with synchronous writes
- ✓ Load-balanced, stateless application tier — rolling deploys with zero downtime
- ✓ Automated capacity scaling for call and meeting spikes
- ✓ Independent region control planes — one region's incident doesn't cascade
Stay informed
Subscribe to the public status page for real-time incident updates and maintenance notices. RSS, email, SMS, Slack, and webhook channels all supported.
Reliability FAQ
What does 99.999% uptime actually mean?
5.26 minutes of allowed downtime per year. Beyond that, customers receive service credits per the SLA schedule. Higher than typical SaaS (99.9% = 8.76 hrs/year) because phone downtime has direct business impact.
What architecture supports 99.999%?
Active-active across 4 US regions (Virginia, Oregon, Texas, Ohio) with automatic failover. Carrier-diverse PSTN peering eliminates single-carrier failures. All critical databases geo-replicated with synchronous writes to 2+ regions.
Where is the status page?
status.dialphone.com — real-time and historical. Subscribe via RSS, email, SMS, Slack, or webhook.
How do I claim service credits?
For qualifying SLA breaches, credits apply automatically to the next invoice. For disputes or questions, contact success@dialphone.com within 60 days of the incident.
How often do you do chaos / game-day testing?
Quarterly, full region failover drills. Monthly, component-level chaos experiments in staging. Findings documented and remediated against published timelines.