User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is OpenCX down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → open.cx—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 151 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 627 ms | 0 |
| Mon 21 | 0 | 0.0 | 194 ms | 0 |
| Mon 23 | 0 | 0.0 | 135 ms | 0 |
| Tue 01 | 0 | 0.0 | 121 ms | 0 |
| Tue 03 | 0 | 0.0 | 168 ms | 0 |
| Tue 05 | 0 | 0.0 | 113 ms | 0 |
| Tue 07 | 0 | 0.0 | 120 ms | 0 |
| Tue 09 | 0 | 0.0 | 143 ms | 0 |
| Tue 12 | 0 | 0.0 | 60 ms | 0 |
| Tue 14 | 0 | 0.0 | 197 ms | 0 |
| Tue 16 | 0 | 0.0 | 587 ms | 0 |
| Tue 18 | 0 | 0.0 | 456 ms | 0 |
| Tue 21 | 0 | 0.0 | 410 ms | 0 |
| Tue 23 | 0 | 0.0 | 109 ms | 0 |
| Wed 01 | 0 | 0.0 | 79 ms | 0 |
| Wed 03 | 0 | 0.0 | 202 ms | 0 |
| Wed 06 | 0 | 0.0 | 423 ms | 0 |
| Wed 08 | 0 | 0.0 | 745 ms | 0 |
| Wed 10 | 0 | 0.0 | 471 ms | 0 |
| Wed 12 | 0 | 0.0 | 140 ms | 0 |
| Wed 14 | 0 | 0.0 | 114 ms | 0 |
| Wed 16 | 0 | 0.0 | 142 ms | 0 |
| Wed 19 | 0 | 0.0 | 122 ms | 0 |
| Wed 21 | 0 | 0.0 | 169 ms | 0 |
| Wed 23 | 0 | 0.0 | 451 ms | 0 |
| Thu 01 | 0 | 0.0 | 935 ms | 0 |
| Thu 03 | 0 | 0.0 | 805 ms | 0 |
| Thu 05 | 0 | 0.0 | 124 ms | 0 |
| Thu 07 | 0 | 0.0 | 583 ms | 0 |
| Thu 09 | 0 | 0.0 | 559 ms | 0 |
| Thu 12 | 0 | 0.0 | 204 ms | 0 |
| Thu 14 | 0 | 0.0 | 880 ms | 0 |
| Thu 16 | 0 | 0.0 | 228 ms | 0 |
| Thu 18 | 0 | 0.0 | 235 ms | 0 |
| Thu 20 | 0 | 0.0 | 433 ms | 0 |
| Thu 21 | 0 | 0.0 | 510 ms | 0 |
| Thu 23 | 0 | 0.0 | 130 ms | 0 |
| Fri 01 | 0 | 0.0 | 1060 ms | 0 |
| Fri 03 | 0 | 0.0 | 124 ms | 0 |
| Fri 05 | 0 | 0.0 | 202 ms | 0 |
| Fri 07 | 0 | 0.0 | 775 ms | 0 |
| Fri 09 | 0 | 0.0 | 735 ms | 0 |
| Fri 11 | 0 | 0.0 | 410 ms | 0 |
| Fri 13 | 0 | 0.0 | 57 ms | 0 |
| Fri 15 | 0 | 0.0 | 417 ms | 0 |
| Fri 17 | 0 | 0.0 | 129 ms | 0 |
| Fri 18 | 0 | 0.0 | 158 ms | 0 |
| Fri 19 | 0 | 0.0 | 151 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live OpenCX badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for OpenCX yet. Outages of 10 minutes or more get their own page here.
Having trouble with OpenCX?
One report per service every 10 minutes from this network. No account.
Follow OpenCX
Get an email when OpenCX goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenCX alerts to Slack, Discord or a webhook — free.
About OpenCX
We track OpenCX (open.cx) as part of the Productivity group. Automate 77% of support tickets with enterprise-grade accuracy, security, and human handoff.
OpenCX publishes an official status page at status.open.cx; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 361 ms average, 57–1060 ms range across 15 successful checks.
Questions
Is OpenCX down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was OpenCX last down?
We have not recorded a public OpenCX incident since monitoring began 8 days ago.
What is OpenCX's uptime?
From our own checks: 100% over 8 days of checks.
How fast does OpenCX respond?
361 ms on average over the last 24 hours (57–1060 ms).
Does OpenCX have an official status page?
Yes, at https://status.open.cx.
OpenCX not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report OpenCX here at once, the problem is on OpenCX's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with OpenCX. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.