User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 28 min ago. Last stored result reached it in 39 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 07 | 0 | 0.0 | 88 ms | 0 |
| Mon 10 | 0 | 0.0 | 126 ms | 0 |
| Mon 12 | 0 | 0.0 | 57 ms | 0 |
| Mon 14 | 0 | 0.0 | 80 ms | 0 |
| Mon 16 | 0 | 0.0 | 109 ms | 0 |
| Mon 18 | 0 | 0.0 | 131 ms | 0 |
| Mon 20 | 0 | 0.0 | 94 ms | 0 |
| Mon 22 | 0 | 0.0 | 52 ms | 0 |
| Tue 00 | 0 | 0.0 | 113 ms | 0 |
| Tue 02 | 0 | 0.0 | 108 ms | 0 |
| Tue 04 | 0 | 0.0 | 41 ms | 0 |
| Tue 07 | 0 | 0.0 | 171 ms | 0 |
| Tue 09 | 0 | 0.0 | 42 ms | 0 |
| Tue 11 | 0 | 0.0 | 112 ms | 0 |
| Tue 13 | 0 | 0.0 | 99 ms | 0 |
| Tue 15 | 0 | 0.0 | 69 ms | 0 |
| Tue 17 | 0 | 0.0 | 78 ms | 0 |
| Tue 20 | 0 | 0.0 | 71 ms | 0 |
| Tue 22 | 0 | 0.0 | 110 ms | 0 |
| Wed 00 | 0 | 0.0 | 93 ms | 0 |
| Wed 02 | 0 | 0.0 | 188 ms | 0 |
| Wed 05 | 0 | 0.0 | 108 ms | 0 |
| Wed 07 | 0 | 0.0 | 70 ms | 0 |
| Wed 09 | 0 | 0.0 | 38 ms | 0 |
| Wed 11 | 0 | 0.0 | 142 ms | 0 |
| Wed 13 | 0 | 0.0 | 86 ms | 0 |
| Wed 15 | 0 | 0.0 | 62 ms | 0 |
| Wed 18 | 0 | 0.0 | 381 ms | 0 |
| Wed 20 | 0 | 0.0 | 41 ms | 0 |
| Wed 22 | 0 | 0.0 | 132 ms | 0 |
| Thu 00 | 0 | 0.0 | 147 ms | 0 |
| Thu 02 | 0 | 0.0 | 141 ms | 0 |
| Thu 04 | 0 | 0.0 | 133 ms | 0 |
| Thu 06 | 0 | 0.0 | 73 ms | 0 |
| Thu 08 | 0 | 0.0 | 114 ms | 0 |
| Thu 10 | 0 | 0.0 | 55 ms | 0 |
| Thu 12 | 0 | 0.0 | 92 ms | 0 |
| Thu 15 | 0 | 0.0 | 54 ms | 0 |
| Thu 17 | 0 | 0.0 | 176 ms | 0 |
| Thu 19 | 0 | 0.0 | 222 ms | 0 |
| Thu 21 | 0 | 0.0 | 72 ms | 0 |
| Thu 23 | 0 | 0.0 | 73 ms | 0 |
| Fri 01 | 0 | 0.0 | 213 ms | 0 |
| Fri 03 | 0 | 0.0 | 135 ms | 0 |
| Fri 05 | 0 | 0.0 | 76 ms | 0 |
| Fri 07 | 0 | 0.0 | 89 ms | 0 |
| Fri 09 | 0 | 0.0 | 39 ms | 0 |
| Fri 11 | 0 | 0.0 | 74 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 CData Cloud 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 CData Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CData Cloud alerts to Slack, Discord or a webhook — free.
CData Cloud is listed in our AI category and checked at cdata.com. Everything enterprise AI depends on, governed from the prompt down to the record.
CData Cloud publishes an official status page at status.cdata.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 110 ms average, 39–222 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CData Cloud incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
110 ms on average over the last 24 hours (39–222 ms).
Yes, at https://status.cdata.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report CData Cloud here at once, the problem is on CData Cloud'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 CData Cloud. 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.