Grain Outage History

24 incidents recorded over the last 365 days, 17 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 Grain status100.00% uptime history

Every Recorded Grain Incident

Grain incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Local capturesDo to a failure with an upstream provider: - 142 local capture sessions failed to begin so nothing was captured - 19 local capture sessions were prematurely truncated so only captured a portion of the meeting The team…-275 minResolved
Oct 28, 2026Spike in unprocessed local capturesAn upstream transcript provider outage caused live transcription to fail for local capture. We have recovered all impacted captures.3h 24mResolved
Oct 21, 2026Google Meet link format changeHotfixes have been deployed across all platforms and testing shows capture is working correctly.1h 59mResolved
Oct 20, 2026Webhook consumers failing causing app failuresAll bot recordings that were left unprocessed due to the outage have been recovered.29h 25mResolved
Sep 16, 2026Transcription Provider OutageThe upstream incident has been resolved, the team will work through the backlog of any impacted recordings for reprocessing.8h 5mResolved
Jul 19, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 18, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 12, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 11, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 5, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jul 4, 2026Planned database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jun 26, 2026Bot Delays and FailuresAn outage with an upstream provider caused recording bots to be delayed or fail to join altogether. The team is investigating potential mitigations for the future.0 minResolved
Jun 25, 2026Transcript Partner OutageAll failed transcripts have been reprocessed.98h 47mResolved
Jun 23, 2026App outageThe team has no observed further issues.6h 25mResolved
Jun 11, 2026Stuck local capturesAll hung local captures were recovered.281h 2mResolved
Jun 11, 2026Bot failuresThe team has not observed any further degradation in the bot service.6h 6mResolved
Jun 2, 2026Bot Recording FailuresAll recordings that were successfully captured have now been recovered. Future improvements around being more robust to upstream failures are being researched by the team.25h 29mResolved
May 13, 2026Recording Processing IssuesAll recordings with recoverable media have now be successfully recovered.34h 20mResolved
May 13, 2026Platform instabilitiyThe team determined the root cause was related to index changes on a hot job queue table, leading to high CPU usage. The correct indexes were applied and the database returned to full health.6h 8mResolved
May 3, 2026Planned MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 24, 2026Failure to start recordingsOur upstream provider has closed their incident. We are no longer observing any instability. Cleanup of captured but unprocessed recordings is underway.4h 25mResolved
Mar 23, 2026Platform InstabilityThe team has deployed a fix around large memory spikes trigging out-of-memory failures. Since the latest fix, no further memory spikes have occurred.101h 54mResolved
Nov 11, 2025Meet Recorder Partial OutageWe have not seen subsequent failures.6h 46mResolved
Nov 6, 2025Incident with upstream provider causing some recorders to failThis incident has been resolved.15h 36mResolved

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 Grain 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 Grain 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 Grain 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 Grain outage in this window ran 11d 17h, against a mean recovery of 1d 3h. If you depend on Grain 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.