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 11 min ago. Last stored result reached it in 533 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 218 ms | 0 |
| Tue 00 | 0 | 0.0 | 584 ms | 0 |
| Tue 02 | 0 | 0.0 | 712 ms | 0 |
| Tue 04 | 0 | 0.0 | 242 ms | 0 |
| Tue 06 | 0 | 0.0 | 499 ms | 0 |
| Tue 08 | 0 | 0.0 | 529 ms | 0 |
| Tue 10 | 0 | 0.0 | 236 ms | 0 |
| Tue 13 | 0 | 0.0 | 552 ms | 0 |
| Tue 15 | 0 | 0.0 | 270 ms | 0 |
| Tue 17 | 0 | 0.0 | 301 ms | 0 |
| Tue 19 | 0 | 0.0 | 276 ms | 0 |
| Tue 22 | 0 | 0.0 | 218 ms | 0 |
| Wed 00 | 0 | 0.0 | 411 ms | 0 |
| Wed 02 | 0 | 0.0 | 251 ms | 0 |
| Wed 04 | 0 | 0.0 | 602 ms | 0 |
| Wed 07 | 0 | 0.0 | 185 ms | 0 |
| Wed 09 | 0 | 0.0 | 345 ms | 0 |
| Wed 11 | 0 | 0.0 | 732 ms | 0 |
| Wed 13 | 0 | 0.0 | 207 ms | 0 |
| Wed 15 | 0 | 0.0 | 331 ms | 0 |
| Wed 17 | 0 | 0.0 | 732 ms | 0 |
| Wed 20 | 0 | 0.0 | 258 ms | 0 |
| Wed 22 | 0 | 0.0 | 204 ms | 0 |
| Thu 00 | 0 | 0.0 | 475 ms | 0 |
| Thu 02 | 0 | 0.0 | 365 ms | 0 |
| Thu 04 | 0 | 0.0 | 221 ms | 0 |
| Thu 06 | 0 | 0.0 | 647 ms | 0 |
| Thu 08 | 0 | 0.0 | 184 ms | 0 |
| Thu 10 | 0 | 0.0 | 498 ms | 0 |
| Thu 13 | 0 | 0.0 | 215 ms | 0 |
| Thu 15 | 0 | 0.0 | 227 ms | 0 |
| Thu 17 | 0 | 0.0 | 276 ms | 0 |
| Thu 19 | 0 | 0.0 | 648 ms | 0 |
| Thu 21 | 0 | 0.0 | 239 ms | 0 |
| Thu 23 | 0 | 0.0 | 190 ms | 0 |
| Fri 01 | 0 | 0.0 | 207 ms | 0 |
| Fri 03 | 0 | 0.0 | 261 ms | 0 |
| Fri 05 | 0 | 0.0 | 197 ms | 0 |
| Fri 07 | 0 | 0.0 | 522 ms | 0 |
| Fri 08 | 0 | 0.0 | 312 ms | 0 |
| Fri 10 | 0 | 0.0 | 220 ms | 0 |
| Fri 12 | 0 | 0.0 | 194 ms | 0 |
| Fri 14 | 0 | 0.0 | 326 ms | 0 |
| Fri 16 | 0 | 0.0 | 505 ms | 0 |
| Fri 18 | 0 | 0.0 | 389 ms | 0 |
| Fri 19 | 0 | 0.0 | 210 ms | 0 |
| Fri 20 | 0 | 0.0 | 234 ms | 0 |
| Fri 22 | 0 | 0.0 | 533 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Uchat 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 Uchat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Uchat alerts to Slack, Discord or a webhook — free.
Uchat is listed in our AI category and checked at uchat.com.au. Build no-code AI agents for WhatsApp, Instagram, Messenger and web. Automate sales and support with visual workflows, integrations and human handoff.
Uchat publishes an official status page at status.uchat.com.au; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 327 ms average, 163–564 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Uchat incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
327 ms on average over the last 24 hours (163–564 ms).
Yes, at https://status.uchat.com.au.
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 Uchat here at once, the problem is on Uchat'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 Uchat. 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.