Historial de interrupciones de Reclaimai

1. 31 de agosto de 2026 a las 20:10 UTCinvestigating

   Microsoft está reportando una degradación del servicio que afecta a Microsoft 365 (Business and Enterprise), incluyendo Outlook y Exchange. Como resultado, sincronización de calendarios y programación puede no funcionar para recuperar clientes conectados a través de una cuenta de Microsoft 365. Este es un problema en el lado de Microsoft, no con Reclaim. Puede seguir el progreso de Microsoft aquí: https://status.cloud.microsoft Actualizaremos este estado a medida que cambie la situación.

2. 31 de agosto de 2026 a las 20:11 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 1 de septiembre de 2026 a las 1:58 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de abril de 2026 a las 1:03 UTCresolved

   A subset of customers who use Reclaim.ai with Slack received a number of duplicate Slack notifications (event reminders, daily digest, etc.).

1. 20 de abril de 2026 a las 18:53 UTCinvestigating

   We are currently investigating an issue where some users are seeing errors when trying to add Zoom as the video conferencing option to Smart Meetings

2. 20 de abril de 2026 a las 20:11 UTCinvestigating

   The issue was identified and a fix was deployed.

3. 20 de abril de 2026 a las 20:12 UTCresolved

   This incident has been resolved.

1. 13 de abril de 2026 a las 10:34 UTCinvestigating

   We are currently investigating this issue.

2. 13 de abril de 2026 a las 11:02 UTCresolved

   There was no issue with calendar sync. All systems are working correclty.

1. 2 de abril de 2026 a las 17:31 UTCinvestigating

   Scheduling Links are currently not loading for users. We are urgently investigating this matter and will provide updates shortly.

2. 2 de abril de 2026 a las 17:36 UTCidentified

   The issue is rooted in an upstream provider outage. We are pursuing mitigation steps.

3. 2 de abril de 2026 a las 17:40 UTCidentified

   A potential mitigation for the issue is being rolled out right now. We will provide another update shortly.

4. 2 de abril de 2026 a las 17:49 UTCmonitoring

   Our failover to a different provider worked and Scheduling Links are back online for all users. We will be monitoring this situation closely throughout the day. We will also conduct a port mortem analysis to learn how we could respond faster to similar issues in the future. Thank you for your patience and understanding.

5. 2 de abril de 2026 a las 17:54 UTCresolved

   This incident has been resolved.

1. 9 de marzo de 2026 a las 12:52 UTCinvestigating

   We’re currently experiencing degraded calendar sync performance. Some calendar updates may be delayed while we investigate and work on a fix.

2. 9 de marzo de 2026 a las 12:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 de marzo de 2026 a las 13:07 UTCidentified

   We’ve identified the issue, and service should return to normal shortly.

4. 9 de marzo de 2026 a las 13:25 UTCresolved

   The issue has been resolved, and calendar sync performance is back to normal.

1. 5 de marzo de 2026 a las 2:22 UTCinvestigating

   We are currently investigating this issue.

2. 5 de marzo de 2026 a las 2:34 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 5 de marzo de 2026 a las 2:44 UTCresolved

   This incident has been resolved.

1. 11 de febrero de 2026 a las 17:18 UTCinvestigating

   Some users may experience a delay on syncs to and from their Google calendars.

2. 11 de febrero de 2026 a las 19:48 UTCresolved

   This incident has been resolved.

1. 9 de febrero de 2026 a las 18:45 UTCinvestigating

   We are currently investigating this issue.

2. 9 de febrero de 2026 a las 19:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 9 de febrero de 2026 a las 19:37 UTCresolved

   This incident has been resolved.

1. 6 de febrero de 2026 a las 23:08 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 7 de febrero de 2026 a las 2:57 UTCidentified

   Tasks and their associated calendar events are in the process of being restored.

3. 7 de febrero de 2026 a las 6:21 UTCresolved

   Tasks and logged time on past events have been restored for most customers.

1. 4 de febrero de 2026 a las 23:08 UTCinvestigating

   We are currently investigating this issue.

2. 4 de febrero de 2026 a las 23:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 de febrero de 2026 a las 23:32 UTCresolved

   This incident has been resolved.

1. 18 de noviembre de 2025 a las 14:00 UTCinvestigating

   We have determined that this is related to an issue with one of our external partners. We are awaiting updates on their end and will update here once this is resolved.

2. 18 de noviembre de 2025 a las 16:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de noviembre de 2025 a las 16:41 UTCmonitoring

   Reclaim may be available via https://app.reclaim.ai without issue. This incident is due to an issue with our upstream provider Cloudflare, impacting much of the internet. Cloudflare is now reporting that services are coming back online and we are monitoring. Track directly at https://www.cloudflarestatus.com/

4. 18 de noviembre de 2025 a las 18:01 UTCresolved

   Cloudflare is reporting all issues have been resolved (https://www.cloudflarestatus.com/) so we are closing this incident, but will continue to monitor as needed.

1. 22 de septiembre de 2025 a las 16:12 UTCinvestigating

   We are aware that the web application and the underlying scheduler is inaccessible for some users.

2. 22 de septiembre de 2025 a las 16:20 UTCmonitoring

   The issue appears to be related to a bad deploy, which has since been rolled back. All systems appear to be fully operational again.

3. 22 de septiembre de 2025 a las 16:55 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2025 a las 18:29 UTCinvestigating

   We are currently investigating this issue.

2. 12 de junio de 2025 a las 19:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 de junio de 2025 a las 19:58 UTCresolved

   This incident has been resolved.

1. 6 de junio de 2025 a las 16:28 UTCresolved

   A small number of users weren't able to book meetings via scheduling links.

1. 2 de junio de 2025 a las 20:21 UTCidentified

   We have identified an issue that is affecting Microsoft Outlook Calendar users and signups, which is preventing the ability to sign up or connect Microsoft Outlook Calendars to Reclaim accounts. Specifically, we've discovered an issue with the Microsoft Graph API where the main /me/calendars endpoint is returning an Internal Server Error (500). This issue is widespread for all services that integrate with Microsoft calendars and is not isolated to Reclaim. We and other companies have raised the issue up with Microsoft and are awaiting a resolution. To see more details about the issue as reported to Microsoft's own forums, please see the following threads: https://learn.microsoft.com/en-us/answers/questions/2279133/getting-500-response-errors-to-get-me-calendars-al https://learn.microsoft.com/en-us/answers/questions/2280408/internal-server-error-alway-as-a-response-for-micr https://learn.microsoft.com/en-us/answers/questions/2280189/i-am-getting-500-internal-server-error-on-https-gr

2. 3 de junio de 2025 a las 0:48 UTCresolved

   This incident has been resolved.

1. 19 de mayo de 2025 a las 15:54 UTCidentified

   Linear is currently experiencing issues causing delays with Reclaim<>Linear sync. Linear has confirmed this on their status page: https://linearstatus.com/

2. 19 de mayo de 2025 a las 15:55 UTCidentified

   We monitoring Linear status and will update when issue is resolved

3. 19 de mayo de 2025 a las 16:11 UTCmonitoring

   Linear has updated their status to operational and we are monitoring/verifying

4. 19 de mayo de 2025 a las 17:20 UTCresolved

   This incident has been resolved.

1. 28 de abril de 2025 a las 16:40 UTCinvestigating

   We are currently investigating this issue.

2. 28 de abril de 2025 a las 16:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de abril de 2025 a las 16:48 UTCresolved

   This incident has been resolved.

1. 6 de abril de 2025 a las 21:44 UTCidentified

   We are aware that Reclaim is acting slowly or inaccessible to some people. A database maintenance we were attempting to do is having trouble. We are working on resolving this issue.

2. 6 de abril de 2025 a las 22:27 UTCidentified

   We are in the middle of rolling back the database upgrade that led to this issue. Until that completes, new users will not be able to sign up and Reclaim will be inaccessible. We apologize for the inconvenience. We will provide another update shortly.

3. 6 de abril de 2025 a las 23:10 UTCmonitoring

   The restore is complete and the application is now loading. The system will need to process changes from calendars and other integrations that happened during this outage. We will provide another update when all that work is complete. Until then, your schedule may appear to be a bit delayed.

4. 6 de abril de 2025 a las 23:57 UTCresolved

   This incident has been resolved.

1. 19 de marzo de 2025 a las 12:52 UTCinvestigating

   We have received reports of delays in syncing in both directions for Microsoft Outlook. We're currently investigating the issue.

2. 19 de marzo de 2025 a las 14:15 UTCidentified

   We are seeing the delays on Microsoft sync decrease, but there are still some delays for some users. We are continuing to mitigate the issue.

3. 19 de marzo de 2025 a las 17:05 UTCidentified

   We are continuing to investigate and resolve the issue impacting delayed Outlook sync. We believe the issue impacts ~20% of the Outlook beta users. A potential fix is being deployed right now and we will continue to monitor the situation.

4. 19 de marzo de 2025 a las 22:32 UTCmonitoring

   A fix has gone out and we are seeing the delayed work is getting processes. We anticipate we will be fully caught up with calendar sync changes in the next 1-2 hours. We will provide another update soon.

5. 19 de marzo de 2025 a las 23:29 UTCresolved

   The backlog has fully processed. We have determined that the core cause of today's incident was due to some (unrelated) database maintenance work we initiated yesterday, which began to have compounding impact on the specific Microsoft Outlook subsystem. We halted the maintenance work and will be exploring other ways to do that work in the future without causing a similar incident. Thank you for your patience as we worked through your Outlook calendar changes today.