30 Attio incidents · gennaio 2024 — official updates, affected components, duration and resolution details.
È stato identificato un problema. Abbiamo identificato la causa principale e il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.
Il problema è stato risolto. Siamo spiacenti per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo indagando i rapporti di ritardi nella formula attributi invalidazioni, il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.
Abbiamo identificato la causa dei ritardi negli aggiornamenti della formula e stiamo lavorando attraverso il backlog. Alcune formule possono continuare a mostrare valori obsoleti fino a quando l'elaborazione non raggiunge.
Una correzione è stata applicata e gli aggiornamenti della formula vengono elaborati di nuovo normalmente. Il backlog rimanente sta raggiungendo e ci aspettiamo che si sgomberi entro l'ora successiva.
Il problema che causa ritardi negli aggiornamenti della formula è stato risolto, e il backlog è stato completamente elaborato. Ci dispiace per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo identificato un problema che sta causando un ritardo a tutti i flussi di lavoro. Stiamo lavorando per riprendere l'elaborazione il più rapidamente possibile e scusarci per qualsiasi inconveniente causato.
Stiamo continuando a rispondere a un incidente che riguarda l'esecuzione del blocco del flusso di lavoro e la consegna webhook.
Stiamo continuando a rispondere a problemi con l'esecuzione del flusso di lavoro e la consegna webhook. Siamo anche consapevoli del potenziale impatto ai sottosistemi di importazione / esportazione e Ask Attio. Stiamo lavorando per ripristinare la disponibilità del servizio.
Il problema che riguarda l'esecuzione del flusso di lavoro e la consegna webhook è stato risolto. Siamo spiacenti per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo indagando sui rapporti di problemi di disponibilità della piattaforma intimitent. Stiamo attualmente indagando sulla causa principale e il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.
Il nostro team ha implementato una correzione per il problema e sta attualmente monitorando il sistema per garantire che il problema sia risolto.
Il problema identificato è stato risolto. Il nostro team ha implementato una correzione per il problema e sta attualmente monitorando il sistema per garantire che il problema sia risolto.
Il problema è stato risolto. Siamo spiacenti per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo indagando sui rapporti dei flussi di lavoro che non si attivano. Stiamo attualmente indagando sulla causa principale e il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.
È stato identificato un problema. Abbiamo identificato la causa principale e il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.
Il nostro team ha implementato una correzione per il problema e sta attualmente monitorando il sistema per garantire che il problema sia risolto.
Tra le 16:33 e le 18:01 UTC il 21 luglio 2026, alcuni flussi di lavoro non hanno attivato correttamente. Che e' successo? Una modifica di configurazione dell'infrastruttura utilizzata poco prima dell'incidente ha causato un errore durante la crittografia del contenuto dei flussi di lavoro appena ricevuti, che ha causato alcuni trigger del flusso di lavoro non funziona correttamente. Cosa abbiamo fatto? Abbiamo reindirizzato il cambiamento e corretto la configurazione dell'infrastruttura sottostante. Tutti i flussi di lavoro influenzati attivano l'elaborazione ripresa normalmente entro 18:01 UTC, e da allora i trigger confermati funzionano correttamente. Stiamo continuando a indagare sul recupero delle piste innescate durante questo periodo di tempo. Aggiorneremo questa pagina non appena avremo un aggiornamento.
La questione è stata risolta e abbiamo comunicato direttamente a tutti i clienti che sono stati colpiti da questo outage. Siamo spiacenti per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'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.
