User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
conductor.is · Cloud & developer
Is Conductor 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 → conductor.is—
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 7 min ago. Last stored result reached it in 242 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 13 | 0 | 0.0 | 204 ms | 0 |
| Mon 15 | 0 | 0.0 | 186 ms | 0 |
| Mon 17 | 0 | 0.0 | 210 ms | 0 |
| Mon 19 | 0 | 0.0 | 167 ms | 0 |
| Mon 21 | 0 | 0.0 | 550 ms | 0 |
| Mon 23 | 0 | 0.0 | 327 ms | 0 |
| Tue 02 | 0 | 0.0 | 175 ms | 0 |
| Tue 04 | 0 | 0.0 | 230 ms | 0 |
| Tue 06 | 0 | 0.0 | 348 ms | 0 |
| Tue 08 | 0 | 0.0 | 252 ms | 0 |
| Tue 10 | 0 | 0.0 | 341 ms | 0 |
| Tue 12 | 0 | 0.0 | 205 ms | 0 |
| Tue 14 | 0 | 0.0 | 162 ms | 0 |
| Tue 17 | 0 | 0.0 | 222 ms | 0 |
| Tue 19 | 0 | 0.0 | 153 ms | 0 |
| Tue 21 | 0 | 0.0 | 160 ms | 0 |
| Tue 23 | 0 | 0.0 | 355 ms | 0 |
| Wed 01 | 0 | 0.0 | 223 ms | 0 |
| Wed 04 | 0 | 0.0 | 290 ms | 0 |
| Wed 06 | 0 | 0.0 | 157 ms | 0 |
| Wed 08 | 0 | 0.0 | 179 ms | 0 |
| Wed 10 | 0 | 0.0 | 367 ms | 0 |
| Wed 13 | 0 | 0.0 | 155 ms | 0 |
| Wed 15 | 0 | 0.0 | 191 ms | 0 |
| Wed 17 | 0 | 0.0 | 496 ms | 0 |
| Wed 19 | 0 | 0.0 | 204 ms | 0 |
| Wed 21 | 0 | 0.0 | 354 ms | 0 |
| Wed 23 | 0 | 0.0 | 187 ms | 0 |
| Thu 02 | 0 | 0.0 | 99 ms | 0 |
| Thu 04 | 0 | 0.0 | 223 ms | 0 |
| Thu 06 | 0 | 0.0 | 217 ms | 0 |
| Thu 08 | 0 | 0.0 | 219 ms | 0 |
| Thu 10 | 0 | 0.0 | 61 ms | 0 |
| Thu 12 | 0 | 0.0 | 638 ms | 0 |
| Thu 14 | 0 | 0.0 | 218 ms | 0 |
| Thu 16 | 0 | 0.0 | 330 ms | 0 |
| Thu 19 | 0 | 0.0 | 187 ms | 0 |
| Thu 21 | 0 | 0.0 | 494 ms | 0 |
| Thu 22 | 0 | 0.0 | 172 ms | 0 |
| Fri 01 | 0 | 0.0 | 255 ms | 0 |
| Fri 03 | 0 | 0.0 | 325 ms | 0 |
| Fri 05 | 0 | 0.0 | 486 ms | 0 |
| Fri 07 | 0 | 0.0 | 240 ms | 0 |
| Fri 09 | 0 | 0.0 | 207 ms | 0 |
| Fri 11 | 0 | 0.0 | 153 ms | 0 |
| Fri 13 | 0 | 0.0 | 201 ms | 0 |
| Fri 15 | 0 | 0.0 | 249 ms | 0 |
| Fri 17 | 0 | 0.0 | 242 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 Conductor 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 Conductor yet. Outages of 10 minutes or more get their own page here.
Having trouble with Conductor?
One report per service every 10 minutes from this network. No account.
Follow Conductor
Get an email when Conductor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Conductor alerts to Slack, Discord or a webhook — free.
About Conductor
We track Conductor (conductor.is) as part of the Cloud & developer group. QuickBooks Desktop API made simple. Connect to QuickBooks Desktop or Enterprise in minutes with Conductor's MCP, Node.js and Python SDKs, and REST API.
Conductor publishes an official status page at status.conductor.is; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 254 ms average, 101–494 ms range across 15 successful checks.
Questions
Is Conductor down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Conductor last down?
We have not recorded a public Conductor incident since monitoring began 7 days ago.
What is Conductor's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Conductor respond?
254 ms on average over the last 24 hours (101–494 ms).
Does Conductor have an official status page?
Yes, at https://status.conductor.is.
Conductor 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 Conductor here at once, the problem is on Conductor'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 Conductor. 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.