OpenCX logo

Is OpenCX Down?

SaaSLive status, outages, and incident history

No. OpenCX is up right now.

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

OperationalChecked 2m agoLive · every 60s

Know the moment OpenCX breaks

OpenCX 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 OpenCX status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

OpenCX Status Summary

As of 18:26 UTC on 14 November 2026, OpenCX is operational. PulsAPI checked OpenCX's official status page and found 7 of 7 components operational, with no active incidents. The latest incident, "Voice AI is down", was on Nov 8, 2026 and lasted 5 min.

Cite as: PulsAPI, “OpenCX status”, checked 14 November 2026, 18:26 UTC. https://www.pulsapi.com/services/opencx

OpenCX Component Status

The main OpenCX systems on this page. All 7 are operational right now.

7operational
Agentic Workflows
Operational
AI Features
Operational
Business Telephony
Operational

4 more components tracked

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

Also tracking Internal APIs, Platform, Public APIs, Voice AI.

See all of them free

Component statuses may change independently during partial outages.

Recent OpenCX Outages & Incidents

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

Voice AI is downResolved Nov 8, 2026 · 5 minResolved
Voice is downResolved Nov 4, 2026 · 14 minResolved
Degraded AI replies for some workspacesResolved Nov 2, 2026 · 50 minResolved

OpenCX Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a OpenCX 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 OpenCX Outage Reports

Problems reported by engineers using OpenCX. 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 OpenCX problems reported yet.

Something wrong with OpenCX on your end?

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

About OpenCX

OpenCX posts its status at status.open.cx. The page covers 7 components, among them AI Features (external provider), Agentic Workflows and Business Telephony (Dialer). Past incidents and uptime for OpenCX stay on this page, which helps when you want to know how often it has trouble.

OpenCX Status FAQ

Is OpenCX down right now?

The verdict at the top of this page comes from the latest poll of the official OpenCX 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 OpenCX 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 OpenCX recovers.

How do I check OpenCX uptime history?

PulsAPI tracks OpenCX 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 OpenCX changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect OpenCX outages?

PulsAPI reads the official OpenCX 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 OpenCX components?

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

Can I get alerts when OpenCX goes down?

Yes. Create a free account and subscribe to OpenCX: 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 OpenCX 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 OpenCX problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor OpenCX?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so OpenCX 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 OpenCX 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