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 19 min ago. Last stored result reached it in 51 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 90 ms | 0 |
| Mon 23 | 0 | 0.0 | 92 ms | 0 |
| Tue 01 | 0 | 0.0 | 65 ms | 0 |
| Tue 03 | 0 | 0.0 | 95 ms | 0 |
| Tue 05 | 0 | 0.0 | 66 ms | 0 |
| Tue 07 | 0 | 0.0 | 46 ms | 0 |
| Tue 09 | 0 | 0.0 | 82 ms | 0 |
| Tue 11 | 0 | 0.0 | 36 ms | 0 |
| Tue 14 | 0 | 0.0 | 34 ms | 0 |
| Tue 16 | 0 | 0.0 | 31 ms | 0 |
| Tue 18 | 0 | 0.0 | 93 ms | 0 |
| Tue 20 | 0 | 0.0 | 66 ms | 0 |
| Tue 23 | 0 | 0.0 | 133 ms | 0 |
| Wed 01 | 0 | 0.0 | 105 ms | 0 |
| Wed 03 | 0 | 0.0 | 53 ms | 0 |
| Wed 05 | 0 | 0.0 | 118 ms | 0 |
| Wed 08 | 0 | 0.0 | 115 ms | 0 |
| Wed 10 | 0 | 0.0 | 33 ms | 0 |
| Wed 12 | 0 | 0.0 | 49 ms | 0 |
| Wed 14 | 0 | 0.0 | 34 ms | 0 |
| Wed 16 | 0 | 0.0 | 62 ms | 0 |
| Wed 18 | 0 | 0.0 | 71 ms | 0 |
| Wed 21 | 0 | 0.0 | 105 ms | 0 |
| Wed 23 | 0 | 0.0 | 59 ms | 0 |
| Thu 01 | 0 | 0.0 | 90 ms | 0 |
| Thu 03 | 0 | 0.0 | 82 ms | 0 |
| Thu 05 | 0 | 0.0 | 77 ms | 0 |
| Thu 07 | 0 | 0.0 | 37 ms | 0 |
| Thu 09 | 0 | 0.0 | 62 ms | 0 |
| Thu 11 | 0 | 0.0 | 34 ms | 0 |
| Thu 13 | 0 | 0.0 | 68 ms | 0 |
| Thu 15 | 0 | 0.0 | 186 ms | 0 |
| Thu 17 | 0 | 0.0 | 100 ms | 0 |
| Thu 19 | 0 | 0.0 | 58 ms | 0 |
| Thu 21 | 0 | 0.0 | 66 ms | 0 |
| Fri 00 | 0 | 0.0 | 188 ms | 0 |
| Fri 02 | 0 | 0.0 | 84 ms | 0 |
| Fri 04 | 0 | 0.0 | 78 ms | 0 |
| Fri 06 | 0 | 0.0 | 62 ms | 0 |
| Fri 08 | 0 | 0.0 | 65 ms | 0 |
| Fri 10 | 0 | 0.0 | 30 ms | 0 |
| Fri 11 | 0 | 0.0 | 43 ms | 0 |
| Fri 13 | 0 | 0.0 | 48 ms | 0 |
| Fri 15 | 0 | 0.0 | 63 ms | 0 |
| Fri 17 | 0 | 0.0 | 87 ms | 0 |
| Fri 19 | 0 | 0.0 | 59 ms | 0 |
| Fri 21 | 0 | 0.0 | 63 ms | 0 |
| Fri 23 | 0 | 0.0 | 51 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 RadAI 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 RadAI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send RadAI alerts to Slack, Discord or a webhook — free.
RadAI, at radai.com, is one of the AI services we monitor. Modern radiology AI for reporting, impressions and follow-up. Reduce cognitive burden, improve report quality and help radiologists work faster.
RadAI publishes an official status page at status.radai.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 71 ms average, 30–188 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public RadAI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
71 ms on average over the last 24 hours (30–188 ms).
Yes, at https://status.radai.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 RadAI here at once, the problem is on RadAI'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 RadAI. 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.