Live / Read AI / Incident
Read AI: Read AI is experiencing a service disruption.
Read AI · read.aiMajor incidentResolved2026-11-03 01:12 UTC
Public — what happened
Summary
Read AI said it had a brief service disruption that it rated as major. The company reported that people could not reach the read.ai website and that its tool could not join some meetings. It said the problem was identified and systems were healthy again, with the degradation lasting from 3:18 to 3:36 PM PST. Read AI said meetings that started in that window may lack reports, while meetings that ended then were being processed, and the incident was marked resolved at 01:12 UTC on November 3.
Affected
Microsoft Teams Meeting Bots, Sign-In, Google Meet Meeting Bots, Read AI Web Application, Create New Account, Zoom Meeting Bots, Google Meet Botless Experience, Read AI Website (https://read.ai)
Timeline
- Started — 2026-11-02 23:59 UTC
- Identified — 2026-11-02 23:59 UTC
- Monitoring — 2026-11-03 00:11 UTC (2 updates)
- Resolved — 2026-11-03 01:12 UTC · 1h 13m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Read AI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Read AI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Read AI report →
More from Read AI
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.