User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Read AI down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft is experiencing a widespread outage
Source: the vendor's status page · We are not affiliated with Read AI.
What to try while Read AI is having problems
Estimated fix: Not enough Read AI 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 → read.ai—
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 2 hr ago. Last stored result reached it in 75 ms.
Official status
Minor incident
Microsoft is experiencing a widespread outage Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 40 ms | 0 |
| Mon 21 | 0 | 0.0 | 79 ms | 0 |
| Mon 23 | 0 | 0.0 | 81 ms | 0 |
| Tue 01 | 0 | 0.0 | 65 ms | 0 |
| Tue 03 | 0 | 0.0 | 36 ms | 0 |
| Tue 05 | 0 | 0.0 | 77 ms | 0 |
| Tue 07 | 0 | 0.0 | 52 ms | 0 |
| Tue 10 | 0 | 0.0 | 79 ms | 0 |
| Tue 12 | 0 | 0.0 | 36 ms | 0 |
| Tue 14 | 0 | 0.0 | 57 ms | 0 |
| Tue 16 | 0 | 0.0 | 88 ms | 0 |
| Tue 19 | 0 | 0.0 | 107 ms | 0 |
| Tue 21 | 0 | 0.0 | 106 ms | 0 |
| Tue 23 | 0 | 0.0 | 34 ms | 0 |
| Wed 01 | 0 | 0.0 | 51 ms | 0 |
| Wed 04 | 0 | 0.0 | 66 ms | 0 |
| Wed 06 | 0 | 0.0 | 52 ms | 0 |
| Wed 08 | 0 | 0.0 | 36 ms | 0 |
| Wed 10 | 0 | 0.0 | 39 ms | 0 |
| Wed 13 | 0 | 0.0 | 62 ms | 0 |
| Wed 15 | 0 | 0.0 | 87 ms | 0 |
| Wed 17 | 0 | 0.0 | 51 ms | 0 |
| Wed 19 | 0 | 0.0 | 101 ms | 0 |
| Wed 21 | 0 | 0.0 | 80 ms | 0 |
| Wed 23 | 0 | 0.0 | 92 ms | 0 |
| Thu 02 | 0 | 0.0 | 128 ms | 0 |
| Thu 03 | 0 | 0.0 | 102 ms | 0 |
| Thu 05 | 0 | 0.0 | 65 ms | 0 |
| Thu 07 | 0 | 0.0 | 29 ms | 0 |
| Thu 09 | 0 | 0.0 | 37 ms | 0 |
| Thu 11 | 0 | 0.0 | 61 ms | 0 |
| Thu 13 | 0 | 0.0 | 50 ms | 0 |
| Thu 16 | 0 | 0.0 | 114 ms | 0 |
| Thu 18 | 0 | 0.0 | 61 ms | 0 |
| Thu 20 | 0 | 0.0 | 53 ms | 0 |
| Thu 21 | 0 | 0.0 | 75 ms | 0 |
| Thu 23 | 0 | 0.0 | 112 ms | 0 |
| Fri 01 | 0 | 0.0 | 67 ms | 0 |
| Fri 03 | 0 | 0.0 | 76 ms | 0 |
| Fri 05 | 0 | 0.0 | 54 ms | 0 |
| Fri 07 | 0 | 0.0 | 47 ms | 0 |
| Fri 09 | 0 | 0.0 | 67 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 14 | 0 | 0.0 | 105 ms | 0 |
| Fri 16 | 0 | 0.0 | 48 ms | 0 |
| Fri 18 | 0 | 0.0 | 142 ms | 0 |
| Fri 20 | 0 | 0.0 | 192 ms | 0 |
| Fri 21 | 0 | 0.0 | 75 ms | 0 |
Reliability
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.
Embed this status: free live Read AI 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 Read AI yet. Outages of 10 minutes or more get their own page here.
Having trouble with Read AI?
One report per service every 10 minutes from this network. No account.
Follow Read AI
Get an email when Read AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Read AI alerts to Slack, Discord or a webhook — free.
About Read AI
We track Read AI (read.ai) as part of the AI group. Read AI, the fastest growing AI meeting notetaker in the world, works wherever you work including Microsoft Teams, Google Meet, Zoom, Claude, ChatGPT, iOS, Android, and Desktop.
Read AI publishes an official status page at status.read.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 86 ms average, 47–192 ms range across 11 successful checks.
Questions
Is Read AI down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft is experiencing a widespread outage
When was Read AI last down?
We have not recorded a public Read AI incident since monitoring began 8 days ago.
What is Read AI's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Read AI respond?
86 ms on average over the last 24 hours (47–192 ms).
Does Read AI have an official status page?
Yes, at https://status.read.ai.
Read AI 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 Read AI here at once, the problem is on Read AI'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 Read AI. 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.