Voxtelesys logo

Is Voxtelesys Down?

CommunicationLive status, outages, and incident history

No. Voxtelesys is up right now.

Every monitored Voxtelesys system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment Voxtelesys breaks

Voxtelesys is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Voxtelesys status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Voxtelesys Status Summary

As of 17:03 UTC on 14 November 2026, Voxtelesys is operational. PulsAPI checked Voxtelesys's official status page and found 16 of 16 components operational, with no active incidents. The latest incident, "SLC Datacenter Power Disruption", was on Oct 26, 2026 and lasted 35h 30m.

Cite as: PulsAPI, “Voxtelesys status”, checked 14 November 2026, 17:03 UTC. https://www.pulsapi.com/services/voxtelesys

Voxtelesys Component Status

The main Voxtelesys systems on this page. All 16 are operational right now.

16operational
911 Services » 911 Call Routing
Operational
911 Services » 911 Provisioning
Operational
API Services
Operational

13 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking eFax » Inbound eFax, eFax » Outbound eFax, Hosted 3CX, Inbound Calling » API Inbound Calling, Inbound Calling » Local DID, Inbound Calling » SIP Inbound Calling, Inbound Calling » Toll Free, Messaging » MMS Messaging, Messaging » SMS Messaging, Outbound Calling » API Outbound Calling, Outbound Calling » SIP Outbound Calling, Portal, and 1 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Voxtelesys Outages & Incidents

Incident history from the official Voxtelesys status page, including resolution updates.

SLC Datacenter Power DisruptionResolved Oct 26, 2026 · 35h 30mResolved

All systems have been fully operational and stable since yesterday morning. The unexpected power loss was isolated to a single rack during a scheduled maintenance window performed by our datacenter facility provider. We are continuing to work directly with the facility provider to review the root cause and prevent future occurrences. 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 --- [2026-10-27T17:49:58.523-05:00] (monitoring) All systems impacted by the power loss have successfully booted and are fully operational. Our engineering team has verified that all clusters are active, and network routing is fully restored. We will continue monitoring all services while we await a formal Reason for Outage (RFO) report from the datacenter. --- [2026-10-27T17:48:51.837-05:00] (identified) We have identified the direct cause of the service disruption in our SLC Datacenter as an unexpected power loss to some equipment during a scheduled maintenance event by the facility provider. Power has been restored to the affected equipment, and systems are coming back online. You may continue to experience degraded performance or connectivity issues while we complete our service check-outs as well as verify 3CX failover systems. Please do not hesitate to contact support if you have questions or concerns. You can create a ticket by emailing support@voxtelesys.com. --- [2026-10-27T18:02:35.252-05:00] (monitoring) We are continuing to monitor the scope of the disruption across the SLC Datacenter to determine the exact equipment affected. Further updates will be provided as soon as we identify the core issue. --- [2026-10-26T06:09:26.565-05:00] (investigating) We are currently investigating alerts of service disruption in our SLC Datacenter.

Voxtelesys Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Voxtelesys incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Voxtelesys Outage Reports

Problems reported by engineers using Voxtelesys. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Voxtelesys problems reported yet.

Something wrong with Voxtelesys on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Voxtelesys

Is Voxtelesys down? Its official status page at status.voxtelesys.com reports on 16 components, including 911 Call Routing, 911 Provisioning and API Services. PulsAPI checks it every few minutes and can alert you when Voxtelesys reports an incident.

Voxtelesys Status FAQ

Is Voxtelesys down right now?

The verdict at the top of this page comes from the latest poll of the official Voxtelesys status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Voxtelesys is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Voxtelesys recovers.

How do I check Voxtelesys uptime history?

PulsAPI tracks Voxtelesys uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Voxtelesys changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Voxtelesys outages?

PulsAPI reads the official Voxtelesys status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Voxtelesys components?

Yes. PulsAPI monitors 16 individual Voxtelesys components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Voxtelesys goes down?

Yes. Create a free account and subscribe to Voxtelesys: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Voxtelesys to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Voxtelesys problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Voxtelesys?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Voxtelesys plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Voxtelesys with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services