Istoricul incidentelor Attio

1. 21 iulie 2026 la 17:35 UTCinvestigating

   Investigăm rapoarte de fluxuri de lucru care nu reuşesc să declanşeze. Investigăm în prezent cauza principală și echipa noastră lucrează pentru a rezolva problema cât mai repede posibil.

2. 21 iulie 2026 la 17:39 UTCidentified

   A fost identificată o problemă. Am identificat cauza principală și echipa noastră lucrează pentru a rezolva problema cât mai repede posibil.

3. 21 iulie 2026 la 18:00 UTCmonitoring

   Echipa noastră a implementat un fix pentru această problemă și monitorizează în prezent sistemul pentru a asigura rezolvarea problemei.

4. 21 iulie 2026 la 20:19 UTCmonitoring

   Între 16:33 și 18:01 UTC la 21 iulie 2026, unele fluxuri de lucru nu au reușit să declanșeze corect. Ce s-a întâmplat? O schimbare a configurației infrastructurii desfășurată cu puțin timp înainte de incident a cauzat o eroare atunci când a criptat conținutul fluxurilor de lucru nou primite, ceea ce a cauzat anumite declanșatoare ale fluxului de lucru care nu funcționează corect. ** Ce am făcut:** Am inversat schimbarea şi am corectat configuraţia infrastructurii. Toate factorii declanşatori de flux de lucru cu impact au fost reporniţi la procesarea normală până la 18:01 UTC, şi de atunci am confirmat că declanşatorii funcţionează corect. Continuăm să investigăm recuperarea rulajelor declanşate în acest interval de timp. Vom actualiza această pagină de îndată ce avem o actualizare.

5. 23 iulie 2026 la 17:29 UTCresolved

   Problema a fost rezolvată acum și am notificat direct toți clienții care au fost afectați de această pană. Ne pare rău pentru orice neplăceri cauzate.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 19:26 UTCresolved

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

1. 19 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 13:06 UTCresolved

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

1. 9 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 17:51 UTCresolved

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

1. 18 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 21:47 UTCresolved

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

1. 30 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 17:19 UTCresolved

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

1. 29 iulie 2025 la 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 iulie 2025 la 17:40 UTCidentified

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

3. 29 iulie 2025 la 22:19 UTCresolved

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

1. 16 iunie 2025 la 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 iunie 2025 la 13:05 UTCresolved

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

1. 12 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 15:39 UTCresolved

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

1. 24 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 15:06 UTCresolved

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

1. 19 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 12:31 UTCresolved

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

1. 24 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 17:25 UTCresolved

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

1. 5 ianuarie 2025 la 19:23 UTCinvestigating

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

2. 7 ianuarie 2025 la 10:39 UTCresolved

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

1. 23 decembrie 2024 la 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 decembrie 2024 la 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 decembrie 2024 la 16:20 UTCresolved

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

1. 3 decembrie 2024 la 07:48 UTCinvestigating

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

2. 3 decembrie 2024 la 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 decembrie 2024 la 16:07 UTCresolved

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

1. 13 noiembrie 2024 la 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 noiembrie 2024 la 19:09 UTCresolved

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

1. 7 august 2024 la 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 august 2024 la 20:29 UTCresolved

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

1. 29 iulie 2024 la 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 iulie 2024 la 12:10 UTCresolved

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

1. 26 iulie 2024 la 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 iulie 2024 la 15:27 UTCresolved

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