User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 43 min ago. Last stored result reached it in 57 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 103 ms | 0 |
| Tue 03 | 0 | 0.0 | 91 ms | 0 |
| Tue 05 | 0 | 0.0 | 47 ms | 0 |
| Tue 07 | 0 | 0.0 | 44 ms | 0 |
| Tue 09 | 0 | 0.0 | 33 ms | 0 |
| Tue 12 | 0 | 0.0 | 38 ms | 0 |
| Tue 14 | 0 | 0.0 | 31 ms | 0 |
| Tue 16 | 0 | 0.0 | 63 ms | 0 |
| Tue 18 | 0 | 0.0 | 81 ms | 0 |
| Tue 21 | 0 | 0.0 | 50 ms | 0 |
| Tue 23 | 0 | 0.0 | 168 ms | 0 |
| Wed 01 | 0 | 0.0 | 56 ms | 0 |
| Wed 03 | 0 | 0.0 | 49 ms | 0 |
| Wed 06 | 0 | 0.0 | 29 ms | 0 |
| Wed 08 | 0 | 0.0 | 58 ms | 0 |
| Wed 10 | 0 | 0.0 | 43 ms | 0 |
| Wed 12 | 0 | 0.0 | 46 ms | 0 |
| Wed 14 | 0 | 0.0 | 53 ms | 0 |
| Wed 16 | 0 | 0.0 | 62 ms | 0 |
| Wed 19 | 0 | 0.0 | 115 ms | 0 |
| Wed 21 | 0 | 0.0 | 23 ms | 0 |
| Wed 23 | 0 | 0.0 | 127 ms | 0 |
| Thu 01 | 0 | 0.0 | 89 ms | 0 |
| Thu 03 | 0 | 0.0 | 70 ms | 0 |
| Thu 05 | 0 | 0.0 | 72 ms | 0 |
| Thu 07 | 0 | 0.0 | 40 ms | 0 |
| Thu 09 | 0 | 0.0 | 92 ms | 0 |
| Thu 12 | 0 | 0.0 | 49 ms | 0 |
| Thu 14 | 0 | 0.0 | 151 ms | 0 |
| Thu 16 | 0 | 0.0 | 40 ms | 0 |
| Thu 18 | 0 | 0.0 | 93 ms | 0 |
| Thu 20 | 0 | 0.0 | 34 ms | 0 |
| Thu 22 | 0 | 0.0 | 59 ms | 0 |
| Fri 00 | 0 | 0.0 | 59 ms | 0 |
| Fri 02 | 0 | 0.0 | 53 ms | 0 |
| Fri 04 | 0 | 0.0 | 128 ms | 0 |
| Fri 06 | 0 | 0.0 | 32 ms | 0 |
| Fri 08 | 0 | 0.0 | 37 ms | 0 |
| Fri 10 | 0 | 0.0 | 48 ms | 0 |
| Fri 12 | 0 | 0.0 | 24 ms | 0 |
| Fri 14 | 0 | 0.0 | 47 ms | 0 |
| Fri 15 | 0 | 0.0 | 52 ms | 0 |
| Fri 17 | 0 | 0.0 | 142 ms | 0 |
| Fri 18 | 0 | 0.0 | 27 ms | 0 |
| Fri 19 | 0 | 0.0 | 51 ms | 0 |
| Fri 20 | 0 | 0.0 | 48 ms | 0 |
| Fri 21 | 0 | 0.0 | 43 ms | 0 |
| Fri 22 | 0 | 0.0 | 57 ms | 0 |
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.
No outages on record for Paradox yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Paradox goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Paradox alerts to Slack, Discord or a webhook — free.
We track Paradox (paradox.ai) as part of the Productivity group. We believe every great hire starts with hello. Our conversational software automates recruiting tasks like screening, interview scheduling, and onboarding to get your candidates from hello to hired faster, and easier, than ever.
Paradox publishes an official status page at status.paradox.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 55 ms average, 23–142 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Paradox incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
55 ms on average over the last 24 hours (23–142 ms).
Yes, at https://status.paradox.ai.
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 Paradox here at once, the problem is on Paradox'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 Paradox. 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.