30 Attio incidents · janvier 2024 — official updates, affected components, duration and resolution details.
Un problème a été relevé. Nous avons identifié la cause fondamentale et notre équipe s'efforce de résoudre le problème le plus rapidement possible.
La question est maintenant réglée. Nous sommes désolés pour tout désagrément causé.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons sur les rapports de retards pour attribuer des invalidations, notre équipe s'efforce de résoudre le problème le plus rapidement possible.
Nous avons identifié la cause des retards dans la mise à jour de la formule et nous travaillons à combler l'arriéré. Certaines formules peuvent continuer à afficher des valeurs dépassées jusqu'à ce que le traitement se rattrape.
Une correction a été appliquée et les mises à jour de la formule sont traitées à nouveau normalement. Le retard restant est en train de rattraper son retard et nous nous attendons à ce qu'il soit comblé d'ici une heure.
La question des mises à jour de la formule a maintenant été résolue et l'arriéré a été entièrement réglé. Nous sommes désolés pour tout désagrément causé.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous avons identifié un problème qui cause un retard à tous les flux de travail. Nous nous efforçons de reprendre le traitement le plus rapidement possible et de nous excuser pour tout inconvénient causé.
Nous continuons de réagir à un incident affectant l'exécution de blocs de workflow et la livraison de webhook.
Nous continuons de répondre aux problèmes liés à l'exécution des flux de travail et à la livraison en ligne. Nous sommes également conscients de l'impact potentiel sur les sous-systèmes importation/exportation ainsi que sur Ask Attio. Nous travaillons à rétablir la disponibilité des services.
La question de l'exécution des flux de travail et de l'exécution des opérations en ligne a été réglée. Nous sommes désolés pour tout désagrément causé.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons sur des rapports sur des problèmes de disponibilité de plateformes intimitentes. Nous enquêtons actuellement sur la cause fondamentale et notre équipe travaille à résoudre le problème le plus rapidement possible.
Notre équipe a déployé un correctif pour le problème et surveille actuellement le système pour s'assurer que le problème est résolu.
Le problème identifié a maintenant été résolu. Notre équipe a déployé un correctif pour le problème et surveille actuellement le système pour s'assurer que le problème est résolu.
La question est maintenant réglée. Nous sommes désolés pour tout désagrément causé.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons sur les rapports de flux de travail qui ne sont pas déclenchés. Nous enquêtons actuellement sur la cause fondamentale et notre équipe travaille à résoudre le problème le plus rapidement possible.
Un problème a été relevé. Nous avons identifié la cause fondamentale et notre équipe s'efforce de résoudre le problème le plus rapidement possible.
Notre équipe a déployé un correctif pour le problème et surveille actuellement le système pour s'assurer que le problème est résolu.
Entre 16:33 et 18:01 UTC le 21 juillet 2026, certains workflows n'ont pas réussi à déclencher correctement. **Ce qui s'est passé:** Un changement de configuration de l'infrastructure déployé peu de temps avant l'incident a causé une erreur lors du cryptage du contenu des flux de travail nouvellement reçus, ce qui a causé certains déclencheurs de flux de travail ne s'exécutant pas correctement. **Ce que nous avons fait:** Nous avons retourné le changement et corrigé la configuration de l'infrastructure sous-jacente. Tous les déclencheurs de workflow touchés ont repris le traitement normalement par 18:01 UTC, et nous avons depuis confirmé que les déclencheurs fonctionnent correctement. Nous continuons d'enquêter sur les opérations de récupération déclenchées pendant cette période. Nous allons mettre à jour cette page dès que nous avons une mise à jour.
Le problème a maintenant été résolu et nous avons informé directement tous les clients qui ont été touchés par cette panne. Nous sommes désolés pour tout désagrément causé.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.
We've identified the issue caused by an upstream provider - our team is working to mitigate the issue as quickly as possible.
The issue has now been resolved. We apologize for any inconvenience caused.
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.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
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.
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.
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
The issue has now been resolved. We apologize for any inconvenience caused.
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.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
We have identified the root cause and our team is working to resolve the issue as quickly as possible.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
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.
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.
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.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating reports of platform availability issues, our team is working to resolve the issue as quickly as possible.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
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.
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.
Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is fully resolved.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are currently investigating a delay in our search indexing system when records are created or updated.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are aware of an issue affecting the speed of CSV Imports. Our team are currently working to resolve the issue.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
We are investigating reports of some Workflows experiencing a delay in executing.
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.
The issue has now been resolved. We’re sorry for any inconvenience caused.
