User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is GetDandy down?
Something is off: our checks are slower than usual or had a single recent failure.
What to try while GetDandy is having problems
Estimated fix: Not enough GetDandy history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
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 → getdandy.com—
Your browser → us—
Our checksSlow or flaky
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
Slow or flaky
Last checked 2 hr ago. Last stored result reached it in 88 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 12 | 0 | 0.0 | 124 ms | 0 |
| Mon 14 | 0 | 0.0 | 51 ms | 0 |
| Mon 16 | 0 | 0.0 | 113 ms | 0 |
| Mon 18 | 0 | 0.0 | 78 ms | 0 |
| Mon 21 | 0 | 0.0 | 70 ms | 0 |
| Mon 23 | 0 | 0.0 | 3433 ms | 0 |
| Tue 01 | 0 | 0.0 | 58 ms | 0 |
| Tue 03 | 0 | 0.0 | 100 ms | 0 |
| Tue 05 | 0 | 0.0 | 2370 ms | 0 |
| Tue 07 | 0 | 0.0 | 2701 ms | 0 |
| Tue 09 | 0 | 0.0 | 2931 ms | 0 |
| Tue 11 | 0 | 0.0 | 80 ms | 0 |
| Tue 14 | 0 | 0.0 | 108 ms | 0 |
| Tue 16 | 0 | 0.0 | 99 ms | 0 |
| Tue 18 | 0 | 0.0 | 2134 ms | 0 |
| Tue 20 | 0 | 0.0 | 1333 ms | 0 |
| Tue 23 | 0 | 0.0 | 90 ms | 0 |
| Wed 01 | 0 | 0.0 | 3918 ms | 0 |
| Wed 03 | 0 | 0.0 | 3223 ms | 0 |
| Wed 05 | 0 | 0.0 | 59 ms | 0 |
| Wed 08 | 0 | 0.0 | 50 ms | 0 |
| Wed 10 | 0 | 0.0 | 32 ms | 0 |
| Wed 12 | 0 | 0.0 | 1959 ms | 0 |
| Wed 14 | 0 | 0.0 | 42 ms | 0 |
| Wed 16 | 0 | 0.0 | 70 ms | 0 |
| Wed 18 | 0 | 0.0 | 110 ms | 0 |
| Wed 21 | 0 | 0.0 | 2180 ms | 0 |
| Wed 23 | 0 | 0.0 | 99 ms | 0 |
| Thu 01 | 0 | 0.0 | 102 ms | 0 |
| Thu 03 | 0 | 0.0 | 2242 ms | 0 |
| Thu 05 | 0 | 0.0 | 2729 ms | 0 |
| Thu 07 | 0 | 0.0 | 67 ms | 0 |
| Thu 09 | 0 | 0.0 | 2043 ms | 0 |
| Thu 11 | 0 | 0.0 | 83 ms | 0 |
| Thu 13 | 0 | 0.0 | 2033 ms | 0 |
| Thu 15 | 0 | 0.0 | 26 ms | 0 |
| Thu 17 | 0 | 0.0 | 52 ms | 0 |
| Thu 19 | 0 | 0.0 | 1924 ms | 0 |
| Thu 22 | 0 | 0.0 | 102 ms | 0 |
| Fri 00 | 0 | 0.0 | 41 ms | 0 |
| Fri 02 | 0 | 0.0 | 58 ms | 0 |
| Fri 04 | 0 | 0.0 | 75 ms | 0 |
| Fri 06 | 0 | 0.0 | 3301 ms | 0 |
| Fri 08 | 0 | 0.0 | 45 ms | 0 |
| Fri 10 | 0 | 0.0 | 1792 ms | 0 |
| Fri 11 | 0 | 0.0 | 1964 ms | 0 |
| Fri 13 | 0 | 0.0 | 1943 ms | 0 |
| Fri 15 | 0 | 0.0 | 88 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 GetDandy 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 GetDandy yet. Outages of 10 minutes or more get their own page here.
Having trouble with GetDandy?
One report per service every 10 minutes from this network. No account.
Follow GetDandy
Get an email when GetDandy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GetDandy alerts to Slack, Discord or a webhook — free.
About GetDandy
GetDandy, at getdandy.com, is one of the AI services we monitor. GetDandy's AI answers every call, gets you more 5-star reviews, and brings in more customers — helping local businesses beat the big brands 24/7.
GetDandy publishes an official status page at status.getdandy.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 882 ms average, 41–3301 ms range across 13 successful checks.
Questions
Is GetDandy down right now?
Something is off: our checks are slower than usual or had a single recent failure.
When was GetDandy last down?
We have not recorded a public GetDandy incident since monitoring began 7 days ago.
What is GetDandy's uptime?
From our own checks: 100% over 7 days of checks.
How fast does GetDandy respond?
882 ms on average over the last 24 hours (41–3301 ms).
Does GetDandy have an official status page?
Yes, at https://status.getdandy.com.
GetDandy 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report GetDandy here at once, the problem is on GetDandy'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 GetDandy. 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.