Historial de interrupciones de Attio

1. July 21, 2026 at 5:35 PM UTCinvestigating

   Estamos investigando informes de flujos de trabajo que no se activan. Actualmente estamos investigando la causa raíz y nuestro equipo está trabajando para resolver el problema lo antes posible.

2. July 21, 2026 at 5:39 PM UTCidentified

   Se ha identificado una cuestión. Hemos identificado la causa raíz y nuestro equipo está trabajando para resolver el problema lo antes posible.

3. July 21, 2026 at 6:00 PM UTCmonitoring

   Nuestro equipo ha implementado una solución para la cuestión y actualmente está monitoreando el sistema para asegurar que la cuestión se resuelva.

4. July 21, 2026 at 8:19 PM UTCmonitoring

   Entre 16:33 y 18:01 UTC el 21 de julio de 2026, algunos flujos de trabajo no activaron correctamente. ¿Qué pasó? Un cambio de configuración de infraestructura desplegado poco antes del incidente causó un error al encriptar el contenido de los flujos de trabajo recién recibidos, lo que causó algunos desencadenantes de flujo de trabajo que no funcionan correctamente. *Lo que hicimos* Revertimos el cambio y corrigimos la configuración de infraestructura subyacente. Todo el flujo de trabajo impactado activa la reanudación del procesamiento normalmente para 18:01 UTC, y desde entonces los desencadenantes confirmados están funcionando correctamente. Continuamos investigando carreras de recuperación activadas durante este período. Actualizaremos esta página tan pronto como tengamos una actualización.

5. July 23, 2026 at 5:29 PM UTCresolved

   El problema ya se ha resuelto y hemos notificado directamente a todos los clientes que fueron afectados por esta salida. Lo sentimos por cualquier inconveniente causado.

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

1. July 10, 2026 at 5:19 PM UTCinvestigating

   We're investigating reports of intimitent errors across some platform features. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. July 10, 2026 at 5:36 PM UTCidentified

   We've identified the issue caused by an upstream provider - our team is working to mitigate the issue as quickly as possible.

3. July 10, 2026 at 7:26 PM UTCresolved

   The issue has now been resolved. We apologize for any inconvenience caused.

1. June 19, 2026 at 10:43 AM UTCidentified

   We’re addressing an issue where some users may be unable to view email content (and in some cases access other stored content like call recordings, file uploads, or exports). We’ve identified the problem and we’re working on a fix now.

2. June 19, 2026 at 10:56 AM UTCmonitoring

   The issue has been resolved. Our team deployed a fix and is monitoring the system to confirm stability. The disruption occurred 08:34 - 09:48 and 10:26 - 10:40 UTC.

3. June 19, 2026 at 1:06 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. December 9, 2025 at 11:50 AM UTCinvestigating

   The Attio team has identified a spike in errors when querying records and lists. Users may experience errors when loading record and list views or when using query endpoints on the public API. We are currently investigating the root cause and working to resolve the issue as quickly as possible.

2. December 9, 2025 at 12:17 PM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. December 9, 2025 at 5:51 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. November 18, 2025 at 11:42 AM UTCinvestigating

   We're investigating reports of intimitent platform availability issues. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. November 18, 2025 at 11:44 AM UTCidentified

   We’re currently experiencing service degradation due to an issue with one of our upstream providers. We’re working closely with them to restore full functionality as soon as possible.

3. November 18, 2025 at 12:15 PM UTCidentified

   We are continuing to work with our upstream provider as they work toward a full resolution. We’ll share further updates as soon as more information becomes available.

4. November 18, 2025 at 2:57 PM UTCmonitoring

   Our upstream provider has resolved the underlying issue, and the platform is now available again. We’re currently working through a backlog of background tasks, but all core functionality has been restored

5. November 18, 2025 at 9:47 PM UTCresolved

   The issue has now been resolved. We apologize for any inconvenience caused.

1. October 30, 2025 at 11:56 AM UTCinvestigating

   We are investigating a system outage that is affecting our realtime sync engine. The realtime engine is responsible for updating information in the UI of our applications as changes are received by our backend. As a workaround, refreshing the page will ensure the latest information is available in the UI.

2. October 30, 2025 at 4:43 PM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. October 30, 2025 at 5:19 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. July 29, 2025 at 5:37 PM UTCinvestigating

   An issue has been identified causing elevated latency in the web app & api. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. July 29, 2025 at 5:40 PM UTCidentified

   We have identified the root cause and our team is working to resolve the issue as quickly as possible.

3. July 29, 2025 at 10:19 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. June 16, 2025 at 6:49 PM UTCinvestigating

   We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. June 17, 2025 at 1:05 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. June 12, 2025 at 6:40 PM UTCinvestigating

   We're aware of an issue with a downstream provider that is impacting platform availability. Our team is working to resolve the issue as quickly as possible.

2. June 12, 2025 at 7:18 PM UTCidentified

   We're currently investigating a major issue with one of our infrastructure providers that's resulting in increased latency for users. A small subset of users may also be unable to access the platform entirely. We're working to resolve this as quickly as possible and will continue to provide updates.

3. June 12, 2025 at 7:36 PM UTCmonitoring

   We're seeing signs of recovery and are closely monitoring the situation. We'll continue to share updates as we receive them from our infrastructure provider.

4. June 12, 2025 at 8:56 PM UTCresolved

   The platform is now fully operational. We’re continuing to monitor our infrastructure provider for any further updates and ongoing stability. Thank you for your patience while we resolved the issue.

1. June 2, 2025 at 10:55 PM UTCidentified

   We have identified an issue that is causing delays in the delivery of outbound email traffic across all email sending functionality (including sequences). The team is actively investigating the root cause of the issue and working to establish mitigations.

2. June 3, 2025 at 3:39 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. April 24, 2025 at 2:17 PM UTCinvestigating

   We are currently investigating reports of platform availability issues, our team is working to resolve the issue as quickly as possible.

2. April 24, 2025 at 2:21 PM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. April 24, 2025 at 3:06 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. April 19, 2025 at 3:34 PM UTCidentified

   An issue has been been identified with our Developer API returning an elevated number of 5xx class errors. Our team is currently investigating and we are working to resolve the issue as quickly as possible.

2. April 19, 2025 at 9:45 PM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. April 23, 2025 at 12:31 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. March 24, 2025 at 3:31 PM UTCinvestigating

   An issue has been been identified. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. March 24, 2025 at 3:36 PM UTCidentified

   An issue has been been identified. We have identified the root cause and our team is working to resolve the issue as quickly as possible.

3. March 24, 2025 at 4:29 PM UTCmonitoring

   Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is fully resolved.

4. March 24, 2025 at 5:25 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. January 5, 2025 at 7:23 PM UTCinvestigating

   We are currently investigating a delay in our search indexing system when records are created or updated.

2. January 7, 2025 at 10:39 AM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. December 23, 2024 at 11:54 AM UTCidentified

   We are aware of an issue affecting the speed of CSV Imports. Our team are currently working to resolve the issue.

2. December 24, 2024 at 1:19 PM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. December 24, 2024 at 4:20 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. December 3, 2024 at 7:48 AM UTCinvestigating

   We are investigating reports of some Workflows experiencing a delay in executing.

2. December 3, 2024 at 11:44 AM UTCmonitoring

   The identified issue has now been resolved. Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. December 9, 2024 at 4:07 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. November 13, 2024 at 5:00 PM UTCidentified

   We have identified an issue affecting the speed at which records become available within search. A mitigation has been deployed and we are continuing to monitor the system as it recovers.

2. November 13, 2024 at 7:09 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. August 7, 2024 at 7:20 PM UTCinvestigating

   An issue has been been identified when attempting to access our marketing and support pages hosted at attio.com We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. August 7, 2024 at 8:29 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. July 29, 2024 at 12:02 PM UTCidentified

   An issue has been been identified. We have identified the root cause and our team is working to resolve the issue as quickly as possible.

2. July 29, 2024 at 12:10 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.

1. July 26, 2024 at 3:22 PM UTCidentified

   We have identified an issue relating to the availability of the Attio Web application. We are working to restore access at this time.

2. July 26, 2024 at 3:27 PM UTCresolved

   The issue has now been resolved. We’re sorry for any inconvenience caused.