Fellow Outage History

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

Every Recorded Fellow Incident

Fellow incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 16, 2026Degraded Meeting NotetakerWe have deploy a remediation and new Meeting Notetaker instances should not experience disruption. Our team continues to monitor the remediation. A subset of notetakers on Google Meet and Teams started over the period…0 minResolved
Oct 1, 2026Increased Latency on Background TasksThe team has remediated the issue and confirmed that the background tasks are being processed at normal rates.1h 38mResolved
Sep 17, 2026Elevated Zoom RTMS issuesThis incident has been resolved.17 minResolved
Sep 1, 2026Delayed transcript generation for calls recorded with botsThe backlog of transcripts has now been processed, and new bots are processing transcripts as expected.1h 3mResolved
Aug 20, 2026Delayed transcript generationOur transcription provider has resolved their incident, and we are seeing transcripts and meeting summaries processing as normal.32 minResolved
Aug 19, 2026Scheduled RTMS MaintenanceMaintenance window in progress. Zoom RTMS calls may fall back to bot-based capture.9h 36mResolved
Aug 18, 2026Increased latencyThis incident has been resolved.24 minResolved
Jul 22, 2026Degraded production availabilityThis incident has been resolved.16 minResolved
Jul 21, 2026Degraded - Glean IntegrationOur system has caught up in processing its backlog. The Glean integration has been restored to normal service levels.1h 57mResolved
Jul 17, 2026Elevated error ratesCloudflare has resolved the incident and we are no longer seeing any errors. Please reach out to customer support if you are still experiencing any issues.2h 49mResolved
Jun 15, 2026Some Zoom meetings may not be recorded or transcribedWe identified an issue that briefly affected meeting recording and transcription for a small number of Zoom meetings earlier today. A fix is in place and the affected component has fully recovered. Recording and…28 minResolved
Jun 14, 2026Degraded Background Task ProcessingThis incident has been resolved. Background tasks are now processing at full capacity1h 25mResolved
Jun 2, 2026Increased LatencyThe incident is resolved.2h 46mResolved
Jun 2, 2026Bot provider outageOur provider has confirmed that this incident has been resolved, and all bots are joining calls normally.2h 5mResolved
May 11, 2026Degraded performanceThis incident has been resolved.2h 1mResolved
Apr 30, 2026Site OutageThis incident has been resolved.15 minResolved
Apr 29, 2026Site outageThis incident has been resolved.10 minResolved
Apr 24, 2026Bots Delayed while Joining Scheduled CallsOur downstream provider has confirmed that their system is back in a healthy condition. There should be no more degradation with respect to join time for scheduled calls.19 minResolved
Apr 18, 2026MCP Returning 404This is now resolved2 minResolved
Apr 17, 2026CloudFlare DNS OutageThe issue shoud be fully resolved now and all fellow.co domains accessable.3h 15mResolved
Apr 14, 2026Increased RTMS errorsThis issue has been resolved. Native Zoom RTMS recording is operating at expected levels14 minResolved
Mar 24, 2026recall.ai outageWe have seen the error rates drop to normal and recording functionality has been restored. We are continuing to monitor and verify all functionality2h 45mResolved
Mar 19, 2026Meeting Recording Status Changes not Reflected in App and Increased LatencyA fix has been deployed and this incident has been resolved.-20 minResolved
Mar 9, 2026Notes editing outageThis incident has been resolved.1h 2mResolved
Jan 7, 2026Notes editing outageThis incident has been resolved.-2730374 minResolved
Jan 7, 2026Notes editing incidentThis incident has been resolved.-2673857 minResolved
Jan 7, 2026Performance degradationThis incident has been resolved.-2632238 minResolved
Jan 7, 2026Notes editing incidentPerformance has been restored. Certain background task deliveries such as Asana and Zapier hooks will be out of sync and require re-triggering.-2543052 minResolved
Jan 7, 2026Performance degradationThe incident is resolved-2460856 minResolved
Jan 7, 2026Notes editing outageThis incident has been resolved.-2441027 minResolved
Jan 7, 2026Performance DegredationThis incident has been resolved.-2430683 minResolved
Jan 7, 2026Elevated errors from certain datacentersThis incident has been resolved.-2406293 minResolved

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 Fellow 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 Fellow 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 Fellow 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 Fellow outage in this window ran 9h 36m, against a mean recovery of 1h 32m. If you depend on Fellow 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.