Critical incident
VOXO: Outbound Calls Failing
Oct 5, 2026, 15:53 UTC
started
15:54 UTC
resolved
1 min
duration
Current status of VOXO: Operational — live VOXO status
Timeline
- Oct 5, 2026, 15:53 UTCidentifiedWe identified an issue in regards to outbound calls failing.
- Oct 5, 2026, 15:54 UTCresolvedWe have resolved the issue in regards to outbound calls failing.
- Oct 5, 2026, 18:52 UTCpostmortem**Summary** On October 5, 2026, starting at approximately 10:40 AM CDT, some customers were unable to place outbound calls. Inbound calling, voicemail, and other services were not affected. The issue was resolved at 10:48 AM CDT. **Cause** A configuration change to our outbound call-routing rules introduced a malformed routing pattern. When our system looked up which carrier to send an outbound call to, that malformed pattern caused the lookup to fail, so calls could not be routed to a carrier and did not connect. **Impact** From approximately 10:40 AM to 10:48 AM CDT \(about 8 minutes\), outbound calls \[for all customers\] failed to connect. Inbound calls were not affected. **Resolution** We corrected the malformed routing rule, which immediately restored outbound calling. To prevent this from happening again, we added validation that rejects malformed routing patterns before they can be saved. We're sorry for the disruption to your day.
Updates as published by VOXO (original).
Other services with incidents at the same time
- Altium 365 16:47 UTC · Incident with Components and Supply Chain
- Kickstarter 15:58 UTC · Login and Signup Prevented due to 3rd Party Outage
- Mews 15:35 UTC · Errors accessing Flexkeeping
- Circle 15:29 UTC · USDC on Linea — Delayed mints and burns (technical difficulties)
- Mews 15:12 UTC · Delays in reservations and channel updates
More VOXO incidents
- October 29, 2026 AI Agent calls degraded
- October 19, 2026 Outbound Calling Degradation
- June 1, 2026 Pharmacy Agent tool failures