Voxtelesys Outage History

Voxtelesys is up right now

Pingoru has recorded 19 incidents for Voxtelesys: 8 in the last 12 months and 0 in the last 90 days.

Source: status.voxtelesys.com

19incidents recorded
8last 12 months
0last 90 days
7 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Voxtelesys in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026216 of 720 (2%)
May 2026212 of 744 (2%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Notice May 8, 2026 Intermittent DFW Network Connectivity 11h 53m

Started May 08, 2026, 04:08 AM UTC· resolved May 08, 2026, 04:01 PM UTC

  1. investigating May 08, 2026, 04:54 AM UTC

    We are investigating an upstream internet provider who is affecting connectivity for some customers.

  2. monitoring May 08, 2026, 05:41 AM UTC

    The upstream providers issue has been mitigated. We have reported the issue and are awaiting response. We will continue to monitor connectivity in the DFW DC.

  3. resolved May 08, 2026, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 6, 2026 Recovered: Transient Hardware Fault on SLC 3CX Server Node 14m

Started May 06, 2026, 03:43 PM UTC· resolved May 06, 2026, 03:58 PM UTC

  1. identified May 06, 2026, 06:46 PM UTC

    A server node in our SLC Datacenter experienced an unexpected transient hardware fault, which briefly affected service for a subset of customers.

  2. resolved May 06, 2026, 06:51 PM UTC

    Our Network Operations team immediately intervened, successfully recovering the server and migrating the affected 3CX instances to a healthy node.

Read the full incident report →

Notice April 20, 2026 Restored: PIT Internal Routing 3h 50m

Started Apr 20, 2026, 07:25 PM UTC· resolved Apr 20, 2026, 11:15 PM UTC

  1. identified Apr 20, 2026, 11:12 PM UTC

    We are addressing a localized routing issue affecting internal traffic within the PIT1 data center.

  2. monitoring Apr 20, 2026, 11:12 PM UTC

    The Network Operations team was able to mitigate the issue by implementing a routing change. We will continue to actively monitor.

  3. resolved Apr 20, 2026, 11:15 PM UTC

    Mitigations via routing change have continued to be stable. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

Read the full incident report →

Notice April 9, 2026 3CX Mobile Push Notification Delivery Issues 12h 8m Hosted 3CX

Started Apr 09, 2026, 12:47 PM UTC· resolved Apr 10, 2026, 12:55 AM UTC

  1. investigating Apr 09, 2026, 02:53 PM UTC

    We are currently investigating reports of some users not receiving push notifications on the 3CX Mobile App.

  2. monitoring Apr 09, 2026, 02:54 PM UTC

    We have identified a connectivity issue affecting some push notification deliveries and have implemented a routing adjustment to bypass the specific external routing irregularity. Immediate testing has shown positive results, and that notifications are delivering successfully. No action is required from your end as we will continue to monitor for stability. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

  3. resolved Apr 10, 2026, 12:55 AM UTC

    There have been no further reports of missing push notifications and all tests continue to pass. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

Read the full incident report →

Minor February 20, 2026 Connectivity Degradation: Cloudflare-Protected 3CX Instances 9h 11m Hosted 3CX

Started Feb 20, 2026, 05:55 PM UTC· resolved Feb 21, 2026, 03:07 AM UTC

  1. investigating Feb 20, 2026, 06:47 PM UTC

    We are investigating monitoring alerts and customer reports of degraded connectivity affecting 3CX instances protected by Cloudflare. Our team is currently coordinating with Cloudflare support to identify the cause and implement a fix.

  2. identified Feb 20, 2026, 06:50 PM UTC

    A workaround is rolling out which should restore connectivity immediately for most users; no manual action is required on your part at this time.

  3. monitoring Feb 20, 2026, 07:18 PM UTC

    Cloudflare's support has confirmed an issue is occurring with its Magic Transit services. Our engineers have had positive test results for the rerouting of traffic around Cloudflare and are proactively monitoring network traffic to ensure this bypass remains effective while we await a final update from Cloudflare on restoration. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

  4. resolved Feb 21, 2026, 03:07 AM UTC

    Cloudflare has reported complete service restoration and officially closed the underlying incident affecting their network. Our network engineering team is maintaining the current network workaround as a proactive measure while we independently verify the stability of their fix. We do not anticipate any further service disruptions related to this event, and we will ensure stability before transitioning traffic back to standard routing.

Read the full incident report →

Major November 18, 2025 Intermittent Service Degradation Due to Upstream Provider Outage 13h 2m Portal, Website, API Services

Started Nov 18, 2025, 11:34 AM UTC· resolved Nov 19, 2025, 12:37 AM UTC

  1. investigating Nov 18, 2025, 02:17 PM UTC

    We are currently investigating an issue with a core networking infrastructure provider that is disrupting access to various services. Our team is actively monitoring the upstream provider's status and their efforts to resolve the connectivity issues. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket via email [email protected]

  2. monitoring Nov 18, 2025, 02:39 PM UTC

    We have implemented a mitigation strategy by migrating DNS services away from the affected provider and actively clearing the cache on major public DNS resolvers. Service availability is currently being verified with positive test results. Access to the website and portal should now be restored; however, due to the nature of DNS propagation, some users may notice a delay before changes take effect. If you continue to experience issues, please attempt to clear your local browser cache or flush your local DNS. We will continue to monitor the situation closely to ensure stability.

  3. monitoring Nov 18, 2025, 02:58 PM UTC

    The upstream provider has reported that a fix is being deployed to their infrastructure. To prioritize stability and prevent potential recurrence, we will maintain our DNS services on the current mitigation path until the upstream incident is fully concluded.

  4. resolved Nov 19, 2025, 12:37 AM UTC

    The upstream provider has confirmed that their services are operating normally and stability has been restored. We have reverted our DNS services to the primary configuration and verified with positive tests. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

Read the full incident report →

Notice November 5, 2025 Resolved: Inbound Call Failure for Some DIDs 36m

Started Nov 05, 2025, 09:30 PM UTC· resolved Nov 05, 2025, 10:06 PM UTC

  1. resolved Nov 06, 2025, 12:21 AM UTC

    A routine configuration update for a subset of DIDs resulted in those numbers being temporarily unable to accept inbound calls. The vast majority of customers were unaffected. The issue was identified and resolved by reverting the problematic configuration change. The service interruption lasted for 36 minutes for the affected DIDs. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

Read the full incident report →

Minor September 9, 2025 Website Service Disruption 8h 48m Portal, Website

Started Sep 09, 2025, 01:18 PM UTC· resolved Sep 09, 2025, 10:06 PM UTC

  1. investigating Sep 09, 2025, 01:18 PM UTC

    We are currently investigating reports that our website is not fully loading for some users. Our engineering team is actively working to identify the root cause of this issue.

  2. monitoring Sep 09, 2025, 01:41 PM UTC

    Our engineering team has implemented a fix for the loading issues, and we are seeing positive test results. We will continue to monitor.

  3. resolved Sep 09, 2025, 10:06 PM UTC

    Our implemented fix has remained stable over the past several hours. We have verified that web content and related services are functioning normally.

Read the full incident report →

Minor June 4, 2025 Intermittent Dropped Connections for West Coast Customers 1d Hosted 3CX

Started Jun 04, 2025, 06:59 PM UTC· resolved Jun 05, 2025, 07:36 PM UTC

  1. investigating Jun 04, 2025, 06:59 PM UTC

    We have received reports of intermittent dropped connections for customers in/around the West Coast. Voxtelesys network engineering is actively investigating the issue, with all available resources dedicated to identifying the scope and resolving the impairment to the network as quickly as possible. Please note our initial investigation indicates the issue is isolated to a specific network peering point, which is affecting customers whose ISPs utilize that connection. Our leadership team is fully engaged, with all network events automatically brought to their attention. We recognize the critical importance of reliable communication, and restoring full service is our top priority.

  2. monitoring Jun 04, 2025, 09:16 PM UTC

    Our network engineering team, in collaboration with upstream transit providers has determined the root cause was external to the Voxtelesys network and our direct providers. The issue stemmed from a transit provider utilized by some affected customers' ISPs, which has now implemented the necessary routing change on their end. Our internal tests show positive results, and connectivity has stabilized. Our team will continue to actively monitor the network to ensure full service restoration and stability for all impacted customers. Please do not hesitate to contact support via ticket if you have questions or concerns. You can create a ticket on our portal: https://portal.voxtelesys.net/support-tickets

  3. resolved Jun 05, 2025, 07:36 PM UTC

    Following our last update, continued monitoring has confirmed that all services have remained stable. A final root cause analysis confirmed the issue was external to Voxtelesys. The source was a network event within Arelion (AS1299). While our IP transit partner, Lumen, took immediate steps to reroute traffic and mitigate the impact, the full resolution was implemented by Arelion’s engineers who corrected the routing on their network. This final corrective action was facilitated by engagement from their direct customers, such as the local ISPs of those who were impacted.

Read the full incident report →

Minor May 22, 2025 Messaging Webhook Delivery Failures 1h 27m SMS Messaging, MMS Messaging

Started May 22, 2025, 07:34 PM UTC· resolved May 22, 2025, 09:02 PM UTC

  1. monitoring May 22, 2025, 07:34 PM UTC

    Our Operations team identified an elevated failure rate affecting messaging MO and DLR webhook deliveries. Upon detection, our Engineering team was promptly engaged and implemented a fix. Webhook deliveries are now completing successfully. We will continue to monitor the situation to ensure continued stability.

  2. resolved May 22, 2025, 09:02 PM UTC

    Monitoring continues to show stability. This incident has been resolved.

Read the full incident report →