Störungsverlauf von Attio

1. 8. September 2026 um 17:05 UTCinvestigating

   Wir untersuchen Berichte über einschüchternde Verfügbarkeitsprobleme der Plattform. Wir untersuchen derzeit die Ursache und unser Team arbeitet daran, das Problem so schnell wie möglich zu lösen.

2. 8. September 2026 um 17:24 UTCmonitoring

   Unser Team hat einen Fix für das Problem bereitgestellt und überwacht derzeit das System, um sicherzustellen, dass das Problem behoben wird.

3. 8. September 2026 um 17:37 UTCmonitoring

   Das identifizierte Problem ist nun gelöst. Unser Team hat einen Fix für das Problem bereitgestellt und überwacht derzeit das System, um sicherzustellen, dass das Problem behoben wird.

4. 8. September 2026 um 18:42 UTCresolved

   Das Problem ist nun gelöst. Es tut uns leid für alle Unannehmlichkeiten, die verursacht wurden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 17:35 UTCinvestigating

   Wir untersuchen Berichte über Workflows, die nicht ausgelöst wurden. Wir untersuchen derzeit die Ursache und unser Team arbeitet daran, das Problem so schnell wie möglich zu lösen.

2. 21. Juli 2026 um 17:39 UTCidentified

   Es wurde ein Problem festgestellt. Wir haben die Ursache identifiziert und unser Team arbeitet daran, das Problem so schnell wie möglich zu lösen.

3. 21. Juli 2026 um 18:00 UTCmonitoring

   Unser Team hat einen Fix für das Problem bereitgestellt und überwacht derzeit das System, um sicherzustellen, dass das Problem behoben wird.

4. 21. Juli 2026 um 20:19 UTCmonitoring

   Zwischen 16:33 und 18:01 UTC am 21. Juli 2026 konnten einige Workflows nicht richtig ausgelöst werden. **Was passiert ist:** Eine kurz vor dem Vorfall bereitgestellte Infrastrukturkonfigurationsänderung verursachte einen Fehler bei der Verschlüsselung des Inhalts neu empfangener Workflows, was dazu führte, dass einige Workflow-Trigger nicht ordnungsgemäß ausgeführt wurden. **Was wir gemacht haben:** Wir haben die Änderung rückgängig gemacht und die zugrunde liegende Infrastrukturkonfiguration korrigiert. Alle betroffenen Workflow-Trigger wurden bis 18:01 UTC wieder normal verarbeitet, und wir haben seitdem bestätigt, dass die Trigger korrekt funktionieren. Wir untersuchen weiterhin Wiederherstellungsläufe, die in diesem Zeitraum ausgelöst wurden. Wir werden diese Seite aktualisieren, sobald wir ein Update haben.

5. 23. Juli 2026 um 17:29 UTCresolved

   Das Problem wurde nun behoben und wir haben alle Kunden, die von diesem Ausfall betroffen waren, direkt benachrichtigt. Es tut uns leid für alle Unannehmlichkeiten, die verursacht wurden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

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

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

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

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

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

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

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

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

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

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

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

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

3. 29. Juli 2025 um 22:19 UTCresolved

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

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

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

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

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

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

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

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

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

1. 24. März 2025 um 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. März 2025 um 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. März 2025 um 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. März 2025 um 17:25 UTCresolved

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

1. 5. Januar 2025 um 19:23 UTCinvestigating

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

2. 7. Januar 2025 um 10:39 UTCresolved

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

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

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

1. 3. Dezember 2024 um 07:48 UTCinvestigating

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

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

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

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

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

1. 7. August 2024 um 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 um 20:29 UTCresolved

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

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

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