Cronologia delle interruzioni di Attio

1. 8 settembre 2026 alle ore 17:05 UTCinvestigating

   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.

2. 8 settembre 2026 alle ore 17:24 UTCmonitoring

   Il nostro team ha implementato una correzione per il problema e sta attualmente monitorando il sistema per garantire che il problema sia risolto.

3. 8 settembre 2026 alle ore 17:37 UTCmonitoring

   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.

4. 8 settembre 2026 alle ore 18:42 UTCresolved

   Il problema è stato risolto. Siamo spiacenti per qualsiasi inconveniente causato.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 21 luglio 2026 alle ore 17:35 UTCinvestigating

   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.

2. 21 luglio 2026 alle ore 17:39 UTCidentified

   È stato identificato un problema. Abbiamo identificato la causa principale e il nostro team sta lavorando per risolvere il problema il più rapidamente possibile.

3. 21 luglio 2026 alle ore 18:00 UTCmonitoring

   Il nostro team ha implementato una correzione per il problema e sta attualmente monitorando il sistema per garantire che il problema sia risolto.

4. 21 luglio 2026 alle ore 20:19 UTCmonitoring

   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.

5. 23 luglio 2026 alle ore 17:29 UTCresolved

   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.

1. 10 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 19:26 UTCresolved

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

1. 19 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 13:06 UTCresolved

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

1. 9 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 17:51 UTCresolved

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

1. 18 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 21:47 UTCresolved

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

1. 30 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 17:19 UTCresolved

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

1. 29 luglio 2025 alle ore 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 luglio 2025 alle ore 17:40 UTCidentified

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

3. 29 luglio 2025 alle ore 22:19 UTCresolved

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

1. 16 giugno 2025 alle ore 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 giugno 2025 alle ore 13:05 UTCresolved

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

1. 12 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 15:39 UTCresolved

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

1. 24 aprile 2025 alle ore 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 aprile 2025 alle ore 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 aprile 2025 alle ore 15:06 UTCresolved

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

1. 19 aprile 2025 alle ore 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 aprile 2025 alle ore 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 aprile 2025 alle ore 12:31 UTCresolved

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

1. 24 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 17:25 UTCresolved

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

1. 5 gennaio 2025 alle ore 19:23 UTCinvestigating

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

2. 7 gennaio 2025 alle ore 10:39 UTCresolved

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

1. 23 dicembre 2024 alle ore 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 dicembre 2024 alle ore 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 dicembre 2024 alle ore 16:20 UTCresolved

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

1. 3 dicembre 2024 alle ore 07:48 UTCinvestigating

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

2. 3 dicembre 2024 alle ore 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 dicembre 2024 alle ore 16:07 UTCresolved

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

1. 13 novembre 2024 alle ore 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 novembre 2024 alle ore 19:09 UTCresolved

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

1. 7 agosto 2024 alle ore 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 agosto 2024 alle ore 20:29 UTCresolved

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

1. 29 luglio 2024 alle ore 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 luglio 2024 alle ore 12:10 UTCresolved

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