Read AI Outage History

26 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Read AI status100.00% uptime history

Every Recorded Read AI Incident

Read AI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Read AI is experiencing a service disruption.This incident has been resolved.1h 12mResolved
Oct 7, 2026Ask Read database maintenanceThe scheduled maintenance has been completed.1h 30mScheduled
Oct 6, 2026Read AI is experiencing an issue with Ask Read.This incident has been resolved.21 minResolved
Oct 1, 2026Read AI Templates are not loadingThis incident has been resolved.1h 26mResolved
Sep 21, 2026Read AI is experiencing an issue with Ask Read.This incident has been resolved.2h 4mResolved
Aug 21, 2026Read AI integrations are experiencing a synchronization issue.This incident has been resolved.3h 2mResolved
Aug 20, 2026Read AI is experiencing delays in meeting report processing.This incident has been resolved.1h 54mResolved
Aug 12, 2026Read AI is experiencing delays in meeting report proccessing.This incident has been resolved.14h 8mResolved
Aug 3, 2026Read AI may not join some Zoom meetingsThis incident has been resolved.3h 8mResolved
Jul 23, 2026Read AI is experiencing an issue joining some meetings.The incident has been resolved.56 minResolved
Jul 7, 2026Issue loading reportsThis incident has been resolved.1h 1mResolved
Jun 22, 2026Read AI is experiencing delays in meeting report proccessing.This incident has been resolved.3h 12mResolved
Jun 18, 2026Calendar Event LoadingService has been restored.2h 57mResolved
Jun 12, 2026Read AI is experiencing degraded bot attendance. We are actively working to mitigate the issue.Systems are operational - Read AI will resume attending meetings as expected.39 minResolved
Jun 11, 20262026-06-11 Elevated OpenAI failure rates.This incident has been resolved.2h 3mResolved
Apr 27, 2026Issues with connecting to Read MCP/API ServerThis incident has been resolved.1h 26mResolved
Apr 20, 20262026-04-20 Elevated report processing errorsThis incident has been resolved.7h 47mResolved
Mar 26, 202603/26/2026 Read AI Is Experiencing Delays in Report GenerationThis incident has been resolved.38 minResolved
Mar 21, 2026Read AI OutageThis incident has been resolved.0 minResolved
Mar 2, 2026Data Processing - Meeting Report GenerationThis incident has been resolved.1h 23mResolved
Feb 12, 2026Read AI AgentsElevated error rates with OpenAI APIs led to increased errors in multiple systems with Read AI.3h 46mResolved
Feb 9, 2026Site InstabilityThis incident has been resolved.7h 30mResolved
Feb 4, 2026Post meeting report processing delaysThis incident has been resolved.3h 2mResolved
Jan 27, 2026Read AI is experiencing delays in sending bots to meetingsThis incident has been resolved.52 minResolved
Jan 21, 2026Post call report processing delaysThis incident has been resolved.3h 54mResolved
Jan 10, 2026Vector DBThe scheduled maintenance has been completed.1h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Read AI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Read AI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Read AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Read AI outage in this window ran 14h 8m, against a mean recovery of 2h 44m. If you depend on Read AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.