User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is CDQ Cloud Services down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with CDQ Cloud Services.
Correction: On Nov 10, 2026 we retracted an incident report for CDQ Cloud Services published in error on Nov 7, 2026. No outage occurred. Read the retraction →
What to try while CDQ Cloud Services is having problems
Estimated fix: Not enough CDQ Cloud Services history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → cdq.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 279 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 275 ms | 0 |
| Mon 22 | 0 | 0.0 | 279 ms | 0 |
| Tue 00 | 0 | 0.0 | 307 ms | 0 |
| Tue 02 | 0 | 0.0 | 299 ms | 0 |
| Tue 04 | 0 | 0.0 | 224 ms | 0 |
| Tue 06 | 0 | 0.0 | 305 ms | 0 |
| Tue 08 | 0 | 0.0 | 228 ms | 0 |
| Tue 10 | 0 | 0.0 | 214 ms | 0 |
| Tue 12 | 0 | 0.0 | 249 ms | 0 |
| Tue 13 | 0 | 0.0 | 188 ms | 0 |
| Tue 15 | 0 | 0.0 | 246 ms | 0 |
| Tue 17 | 0 | 0.0 | 263 ms | 0 |
| Tue 19 | 0 | 0.0 | 227 ms | 0 |
| Tue 22 | 0 | 0.0 | 237 ms | 0 |
| Wed 00 | 0 | 0.0 | 245 ms | 0 |
| Wed 02 | 0 | 0.0 | 315 ms | 0 |
| Wed 04 | 0 | 0.0 | 258 ms | 0 |
| Wed 06 | 0 | 0.0 | 243 ms | 0 |
| Wed 09 | 0 | 0.0 | 199 ms | 0 |
| Wed 11 | 0 | 0.0 | 271 ms | 0 |
| Wed 13 | 0 | 0.0 | 238 ms | 0 |
| Wed 14 | 0 | 0.0 | 270 ms | 0 |
| Wed 16 | 0 | 0.0 | 270 ms | 0 |
| Wed 18 | 0 | 0.0 | 196 ms | 0 |
| Wed 20 | 0 | 0.0 | 268 ms | 0 |
| Wed 22 | 0 | 0.0 | 243 ms | 0 |
| Thu 01 | 0 | 0.0 | 305 ms | 0 |
| Thu 03 | 0 | 0.0 | 254 ms | 0 |
| Thu 04 | 0 | 0.0 | 301 ms | 0 |
| Thu 06 | 0 | 0.0 | 249 ms | 0 |
| Thu 08 | 0 | 0.0 | 264 ms | 0 |
| Thu 10 | 0 | 0.0 | 240 ms | 0 |
| Thu 12 | 0 | 0.0 | 289 ms | 0 |
| Thu 15 | 0 | 0.0 | 309 ms | 0 |
| Thu 17 | 0 | 0.0 | 283 ms | 0 |
| Thu 19 | 0 | 0.0 | 259 ms | 0 |
| Thu 21 | 0 | 0.0 | 274 ms | 0 |
| Thu 23 | 0 | 0.0 | 271 ms | 0 |
| Fri 01 | 0 | 0.0 | 284 ms | 0 |
| Fri 03 | 0 | 0.0 | 345 ms | 0 |
| Fri 05 | 0 | 0.0 | 243 ms | 0 |
| Fri 07 | 0 | 0.0 | 263 ms | 0 |
| Fri 09 | 0 | 0.0 | 290 ms | 0 |
| Fri 11 | 0 | 0.0 | 239 ms | 0 |
| Fri 12 | 0 | 0.0 | 248 ms | 0 |
| Fri 14 | 0 | 0.0 | 244 ms | 0 |
| Fri 16 | 0 | 0.0 | 271 ms | 0 |
| Fri 17 | 0 | 0.0 | 255 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live CDQ Cloud Services 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 CDQ Cloud Services yet. Outages of 10 minutes or more get their own page here.
Having trouble with CDQ Cloud Services?
One report per service every 10 minutes from this network. No account.
Follow CDQ Cloud Services
Get an email when CDQ Cloud Services goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CDQ Cloud Services alerts to Slack, Discord or a webhook — free.
About CDQ Cloud Services
CDQ Cloud Services is listed in our Cloud & developer category and checked at cdq.com. CDQ enables large enterprises to tackle master data quality and data maintenance efforts collaboratively with innovative software solutions.
CDQ Cloud Services publishes an official status page at status.cdq.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 267 ms average, 231–345 ms range across 14 successful checks.
Questions
Is CDQ Cloud Services down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was CDQ Cloud Services last down?
We have not recorded a public CDQ Cloud Services incident since monitoring began 7 days ago.
What is CDQ Cloud Services's uptime?
From our own checks: 100% over 7 days of checks.
How fast does CDQ Cloud Services respond?
267 ms on average over the last 24 hours (231–345 ms).
Does CDQ Cloud Services have an official status page?
Yes, at https://status.cdq.com.
CDQ Cloud Services 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report CDQ Cloud Services here at once, the problem is on CDQ Cloud Services'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 CDQ Cloud Services. 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.