Reclaim Outage History
14 incidents recorded over the last 365 days, 12 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.
Every Recorded Reclaim Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 31, 2026 | Microsoft 365 outage affecting some connected accountsThis incident has been resolved. | 5h 47m | Resolved |
| Apr 24, 2026 | Duplicate Slack notifications sentA subset of customers who use Reclaim.ai with Slack received a number of duplicate Slack notifications (event reminders, daily digest, etc.). | -33 min | Resolved |
| Apr 20, 2026 | Reclaim Platform MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 20, 2026 | Unable to add Zoom to new Smart MeetingsThis incident has been resolved. | 1h 18m | Resolved |
| Apr 13, 2026 | Degraded Calendar Sync PerformanceThere was no issue with calendar sync. All systems are working correclty. | 28 min | Resolved |
| Apr 2, 2026 | Scheduling Links was returning 404 missing links; resolved nowThis incident has been resolved. | 23 min | Resolved |
| Mar 9, 2026 | Degraded Calendar Sync PerformanceThe issue has been resolved, and calendar sync performance is back to normal. | 33 min | Resolved |
| Mar 5, 2026 | Degraded PerformanceThis incident has been resolved. | 22 min | Resolved |
| Mar 2, 2026 | Reclaim Platform Maintenance - 03-01-26 @ 16:30 PSTThe scheduled maintenance has been completed. | 59 min | Scheduled |
| Feb 11, 2026 | Google Calendar Sync DelaysThis incident has been resolved. | 2h 29m | Resolved |
| Feb 9, 2026 | Reclaim Planner slow to load / sporadic errors for subset of usersThis incident has been resolved. | 52 min | Resolved |
| Feb 6, 2026 | Todoist Active Tasks DesyncTasks and logged time on past events have been restored for most customers. | 7h 12m | Resolved |
| Feb 4, 2026 | Todoist Integration Performance DegradationThis incident has been resolved. | 24 min | Resolved |
| Nov 18, 2025 | Intermittent access issues affecting ReclaimCloudflare is reporting all issues have been resolved (https://www.cloudflarestatus.com/) so we are closing this incident, but will continue to monitor as needed. | 4h 0m | Resolved |
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 Reclaim 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 Reclaim 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 Reclaim 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 Reclaim outage in this window ran 7h 12m, against a mean recovery of 1h 59m. If you depend on Reclaim 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.