Histórico de interrupções do Attio

1. 21 Gouere 2026 da 17:35 UTCinvestigating

   Estamos a investigar relatórios de fluxos de trabalho que não disparam. Atualmente estamos investigando a causa básica e nossa equipe está trabalhando para resolver o problema o mais rápido possível.

2. 21 Gouere 2026 da 17:39 UTCidentified

   Foi identificado um problema. Identificamos a causa básica e nossa equipe está trabalhando para resolver o problema o mais rápido possível.

3. 21 Gouere 2026 da 18:00 UTCmonitoring

   Nossa equipe implantou uma correção para o problema e atualmente estão monitorando o sistema para garantir que o problema seja resolvido.

4. 21 Gouere 2026 da 20:19 UTCmonitoring

   Entre 16:33 e 18:01 UTC em 21 de julho de 2026, alguns fluxos de trabalho não conseguiram disparar corretamente. ** O que aconteceu:** Uma mudança de configuração de infraestrutura implantada pouco antes do incidente causar um erro ao criptografar o conteúdo de fluxos de trabalho recém-recebidos, o que causou alguns gatilhos de fluxo de trabalho não serem executados corretamente. ** O que fizemos:** Revertemos a alteração e corrigimos a configuração de infraestrutura subjacente. Todos os gatilhos de fluxo de trabalho impactados retomaram o processamento normalmente às 18:01 UTC, e desde então os gatilhos confirmados estão funcionando corretamente. Continuamos a investigar as operações de recuperação desencadeadas durante este período de tempo. Atualizaremos esta página assim que tivermos uma atualização.

5. 23 Gouere 2026 da 17:29 UTCresolved

   A questão foi agora resolvida e nós temos notificado diretamente todos os clientes que foram impactados por esta falha. Lamentamos qualquer inconveniente causado.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 17:19 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. 10 Gouere 2026 da 17:36 UTCidentified

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

3. 10 Gouere 2026 da 19:26 UTCresolved

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

1. 19 Mezheven 2026 da 10:43 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. 19 Mezheven 2026 da 10:56 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. 19 Mezheven 2026 da 13:06 UTCresolved

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

1. 9 Kerzu 2025 da 11:50 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. 9 Kerzu 2025 da 12:17 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. 9 Kerzu 2025 da 17:51 UTCresolved

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

1. 18 Du 2025 da 11:42 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. 18 Du 2025 da 11:44 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. 18 Du 2025 da 12:15 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. 18 Du 2025 da 14:57 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. 18 Du 2025 da 21:47 UTCresolved

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

1. 30 Here 2025 da 11:56 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. 30 Here 2025 da 16:43 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. 30 Here 2025 da 17:19 UTCresolved

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

1. 29 Gouere 2025 da 17:37 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. 29 Gouere 2025 da 17:40 UTCidentified

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

3. 29 Gouere 2025 da 22:19 UTCresolved

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

1. 16 Mezheven 2025 da 18:49 UTCinvestigating

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

2. 17 Mezheven 2025 da 13:05 UTCresolved

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

1. 12 Mezheven 2025 da 18:40 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. 12 Mezheven 2025 da 19:18 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. 12 Mezheven 2025 da 19:36 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. 12 Mezheven 2025 da 20:56 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. 2 Mezheven 2025 da 22:55 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. 3 Mezheven 2025 da 15:39 UTCresolved

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

1. 24 Ebrel 2025 da 14:17 UTCinvestigating

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

2. 24 Ebrel 2025 da 14:21 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. 24 Ebrel 2025 da 15:06 UTCresolved

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

1. 19 Ebrel 2025 da 15:34 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. 19 Ebrel 2025 da 21:45 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. 23 Ebrel 2025 da 12:31 UTCresolved

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

1. 24 Meurzh 2025 da 15:31 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. 24 Meurzh 2025 da 15:36 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. 24 Meurzh 2025 da 16:29 UTCmonitoring

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

4. 24 Meurzh 2025 da 17:25 UTCresolved

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

1. 5 Genver 2025 da 19:23 UTCinvestigating

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

2. 7 Genver 2025 da 10:39 UTCresolved

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

1. 23 Kerzu 2024 da 11:54 UTCidentified

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

2. 24 Kerzu 2024 da 13:19 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. 24 Kerzu 2024 da 16:20 UTCresolved

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

1. 3 Kerzu 2024 da 07:48 UTCinvestigating

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

2. 3 Kerzu 2024 da 11:44 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. 9 Kerzu 2024 da 16:07 UTCresolved

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

1. 13 Du 2024 da 17:00 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. 13 Du 2024 da 19:09 UTCresolved

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

1. 7 Eost 2024 da 19:20 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. 7 Eost 2024 da 20:29 UTCresolved

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

1. 29 Gouere 2024 da 12:02 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. 29 Gouere 2024 da 12:10 UTCresolved

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

1. 26 Gouere 2024 da 15:22 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. 26 Gouere 2024 da 15:27 UTCresolved

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