30 incidentes de Attio registrados desde enero de 2024, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.
Se ha identificado una cuestión. Hemos identificado la causa raíz y nuestro equipo está trabajando para resolver el problema lo antes posible.
La cuestión ya se ha resuelto. Lo sentimos por cualquier inconveniente causado.
Traducido automáticamente desde la actualización oficial del incidente.
Estamos investigando informes de retrasos a las invalidaciones de atributos de fórmula, nuestro equipo está trabajando para resolver el problema lo antes posible.
Hemos identificado la causa de los retrasos a las actualizaciones de fórmulas y estamos trabajando a través del atraso. Algunas fórmulas pueden seguir mostrando valores obsoletos hasta que el procesamiento se ponga al día.
Se ha aplicado una solución y las actualizaciones de fórmula se procesan normalmente de nuevo. El atraso restante se está recuperando y esperamos que se despeje dentro de la hora siguiente.
Se ha resuelto la cuestión que ocasiona demoras a las actualizaciones de fórmulas, y el atraso se ha tramitado plenamente. Lo sentimos por cualquier inconveniente causado.
Traducido automáticamente desde la actualización oficial del incidente.
Hemos identificado una cuestión que está causando un retraso en todos los flujos de trabajo. Estamos trabajando para reanudar el procesamiento lo más rápido posible y pedir disculpas por cualquier inconveniente causado.
Continuamos respondiendo a un incidente que afecta a la ejecución de bloques de flujo de trabajo y la entrega de webhook.
Seguimos respondiendo a cuestiones relacionadas con la ejecución del flujo de trabajo y la entrega de webhook. También somos conscientes del impacto potencial para los subsistemas de importación / exportación, así como Ask Attio. Estamos trabajando para restaurar la disponibilidad de servicio.
Se ha resuelto la cuestión que afecta a la ejecución del flujo de trabajo y la entrega de webhook. Lo sentimos por cualquier inconveniente causado.
Traducido automáticamente desde la actualización oficial del incidente.
Estamos investigando informes de problemas de disponibilidad de plataformas intimientes. Actualmente estamos investigando la causa raíz y nuestro equipo está trabajando para resolver el problema lo antes posible.
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.
La cuestión identificada se ha resuelto ahora. 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.
La cuestión ya se ha resuelto. Lo sentimos por cualquier inconveniente causado.
Traducido automáticamente desde la actualización oficial del incidente.
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.
Se ha identificado una cuestión. Hemos identificado la causa raíz y nuestro equipo está trabajando para resolver el problema lo antes posible.
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.
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.
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.
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.
