pingoru pingoru VOXO had 22 outages in the last 2 years totaling 23h 20m of downtime, averaging 0.9 incidents per month.
There were 22 VOXO outages since November 8, 2024 totaling 23h 20m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are currently experiencing an issue affecting outbound calls. Users may encounter failures or call drops when attempting to place external calls. Incoming calls remain unaffected. Our team is investigating.
The issue affecting outbound calling has been resolved. All call services are fully operational. We apologize for any inconvenience.
We identified an issue in regards to outbound calls failing.
We have resolved the issue in regards to outbound calls failing.
**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.
The account selector and account settings function in the admin portal are experiencing issues. Our team is investigating the issue.
We have identified the cause linked to a third party provider along the settings route path.
We have narrowed down the degraded request to our attempt to pull billing detail along the account settings path. We are planning to implement an override to restore performance while the third party resolves the issue.
We have implemented a fix to resolve the issue and restore performance. Account settings around billing will be temporarily unavailable until the third-party service provider is operational again.
We are experiencing system-wide issues reaching Liberty Rx server APIs. The issue is being investigated.
The incident was identified with the Liberty Rx team and resolved
Our central region media services experienced a resource exhaustion, resulting in failed media handling in this regions. Customer impacts included calling outages, and stateful issues related to parking lots. The resource issue was identified and resolved at approximately 9:20 AM CDT.
An issue affecting clients with conduit dialing caused interruption for some outbound calling features. The root cause was determine as a system issue related to proper conduit selection and routing. A patch was deployed at approximately 9:00 AM fully addressing the issue.
We discovered an issue causing normal tool functionality for the agent related to status check and refills failing. The root cause was determined and a patch was issued.
Some SIP traffic was found to be targeting a terminating resource, causing some calls to fail.
We're currently aware of a DNS certificate issue affecting some VOXO services. Our team is actively working on a fix, and we'll keep you updated as we make progress. Thank you for your patience!
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved. Please contact support for any issues.
We are experiencing an issue with services causing network disruption. We are monitoring the provider and will provide updates accordingly.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The DNS issue has been resolved and services are restored. Please contact support if you are continuing to experience issues.
At approximately 7:00pm Central Time we experience call delivery failures origination from our southern region. The issue was determined to be due to our southern region sip proxy losing awareness of available media servers. Services have been fully restored and we are continuing to monitor traffic to this region.
Between 10:00 AM and 10:30 AM CST, a subset of outbound calls utilizing business hour routing experienced intermittent failures, preventing some calls from completing successfully. The issue has been resolved and we are sorry for the inconvenience.
We are investigating an issue with degraded service in inbound and outbound calling features.
We have identified some issues causing service degradation. The team is working on a solution.
Services have been restored.
Degraded telecom functionality related to core infrastructure. The team is restoring service and investigating the cause.
We have identified the cause. Affected services are actively being restored. The impact was identified to firmly affect traffic to our central deployment regions. No other traffic regions were determined to be impacted.
All services have been restored.
Failed automation functions for refill tooling for Pharmacy IVR and Agent products.
Service degradation and partial outages will be observed due to service provider global outage.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of issues affecting parking capabilities.
This incident has been resolved.
Connect desktop application not operational for some customers.
We are currently investigating this issue.
Outbound calling is now operational. We are continuing to investigate all other components.
Services are now fully operational. We are continuing to monitor critical systems.
This incident has been resolved.
We are currently experiencing an infrastructure-level disruption affecting access to our historical call data. This is due to an outage with one of our upstream cloud service providers, which is impacting the systems responsible for storing and retrieving historical reporting data. Real-time services are unaffected, but any dashboards, reports, or tools that rely on historical data may not display correctly during this time. Our engineering team is actively working with the provider to restore service as quickly as possible. We will continue to post updates here as more information becomes available. We appreciate your patience.
Historical data can now be accessed. We will continue to monitor for any other degradation to historical data.
This incident has been resolved.
We observed a brief period of intermittent BLF (Busy Lamp Field) issues in one of our datacenter regions, which affected features such as call parking and status updates on desk phones. The issue has been resolved, and services are now functioning as expected. If you continue to experience any BLF-related concerns, please don’t hesitate to contact our support team for assistance by calling 601-602-5060, or emailing [email protected].
This incident has been resolved.
An account experienced a compromise of its admin credentials, resulting in a high volume of outbound SMS messages. This activity temporarily impacted our API's response time. We quickly intervened to halt the issue, and normal performance has since been restored. Please be assured that there was no compromise within VOXO’s systems. Thank you for your understanding and patience.
This incident has been resolved and our API is now operating at full performance.