Attio 장애 기록

1. 2026년 9월 8일 PM 5:05 UTCinvestigating

   Intimitent 플랫폼 가용성 문제의 조사 보고서입니다. 우리는 현재 뿌리 원인을 조사하고 우리의 팀은 가능한 한 빨리 문제를 해결하기 위해 노력하고 있습니다.

2. 2026년 9월 8일 PM 5:24 UTCmonitoring

   우리의 팀은 문제점을 위한 고침을 배치하고 현재 문제를 해결하기 위하여 체계를 감시하고 있습니다.

3. 2026년 9월 8일 PM 5:37 UTCmonitoring

   확인된 문제는 이제 해결되었습니다. 우리의 팀은 문제점을 위한 고침을 배치하고 현재 문제를 해결하기 위하여 체계를 감시하고 있습니다.

4. 2026년 9월 8일 PM 6:42 UTCresolved

   문제는 해결되었습니다. 불편을 드려 죄송합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 PM 5:35 UTCinvestigating

   우리는 트리거에 실패하는 작업 흐름의 조사 보고서입니다. 우리는 현재 뿌리 원인을 조사하고 우리의 팀은 가능한 한 빨리 문제를 해결하기 위해 노력하고 있습니다.

2. 2026년 7월 21일 PM 5:39 UTCidentified

   문제가 확인되었습니다. 우리는 뿌리 원인을 확인하고 우리의 팀은 가능한 한 빨리 문제를 해결하기 위해 노력하고 있습니다.

3. 2026년 7월 21일 PM 6:00 UTCmonitoring

   우리의 팀은 문제점을 위한 고침을 배치하고 현재 문제를 해결하기 위하여 체계를 감시하고 있습니다.

4. 2026년 7월 21일 PM 8:19 UTCmonitoring

   사이 16:33 과 18:01 UTC 에 7월 21, 2026, 일부 작업 흐름은 제대로 트리거에 실패. ** 일어난 일: ** 이 웹 사이트는 귀하가 웹 사이트를 탐색하는 동안 귀하의 경험을 향상시키기 위해 쿠키를 사용합니다. 이 쿠키들 중에서 필요에 따라 분류 된 쿠키는 웹 사이트의 기본적인 기능을 수행하는 데 필수적이므로 브라우저에 저장됩니다. 또한이 웹 사이트의 사용 방식을 분석하고 이해하는 데 도움이되는 제 3 자 쿠키를 사용합니다. 이 쿠키는 귀하의 동의하에 만 브라우저에 저장됩니다. 이러한 쿠키 중 일부를 선택 해제하면 검색 환경에 영향을 미칠 수 있습니다. ** 우리는 무엇을했다 : ** 우리는 변화와 올바른 인프라 구성을 거쳤습니다. 모든 충격 워크 트리거는 일반적으로 18:01 UTC에 의해 처리 된 후, 우리는 확인 된 트리거가 올바르게 작동하기 때문에. 이 시간 동안 회복을 계속 조사하고 있습니다. 이 페이지를 업데이트합니다.

5. 2026년 7월 23일 PM 5:29 UTCresolved

   문제는 이제 해결되었습니다. 우리는이 정전에 영향을받은 모든 고객을 직접 통보했습니다. 불편을 드려 죄송합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 PM 5: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. 2026년 7월 10일 PM 5: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. 2026년 7월 10일 PM 7:26 UTCresolved

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

1. 2026년 6월 19일 AM 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. 2026년 6월 19일 AM 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. 2026년 6월 19일 PM 1:06 UTCresolved

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

1. 2025년 12월 9일 AM 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. 2025년 12월 9일 PM 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. 2025년 12월 9일 PM 5:51 UTCresolved

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

1. 2025년 11월 18일 AM 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. 2025년 11월 18일 AM 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. 2025년 11월 18일 PM 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. 2025년 11월 18일 PM 2: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. 2025년 11월 18일 PM 9:47 UTCresolved

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

1. 2025년 10월 30일 AM 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. 2025년 10월 30일 PM 4: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. 2025년 10월 30일 PM 5:19 UTCresolved

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

1. 2025년 7월 29일 PM 5: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. 2025년 7월 29일 PM 5:40 UTCidentified

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

3. 2025년 7월 29일 PM 10:19 UTCresolved

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

1. 2025년 6월 16일 PM 6:49 UTCinvestigating

   We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. 2025년 6월 17일 PM 1:05 UTCresolved

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

1. 2025년 6월 12일 PM 6: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. 2025년 6월 12일 PM 7: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. 2025년 6월 12일 PM 7: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. 2025년 6월 12일 PM 8: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. 2025년 6월 2일 PM 10: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. 2025년 6월 3일 PM 3:39 UTCresolved

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

1. 2025년 4월 24일 PM 2:17 UTCinvestigating

   We are currently investigating reports of platform availability issues, our team is working to resolve the issue as quickly as possible.

2. 2025년 4월 24일 PM 2: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. 2025년 4월 24일 PM 3:06 UTCresolved

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

1. 2025년 4월 19일 PM 3: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. 2025년 4월 19일 PM 9: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. 2025년 4월 23일 PM 12:31 UTCresolved

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

1. 2025년 3월 24일 PM 3: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. 2025년 3월 24일 PM 3: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. 2025년 3월 24일 PM 4: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. 2025년 3월 24일 PM 5:25 UTCresolved

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

1. 2025년 1월 5일 PM 7:23 UTCinvestigating

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

2. 2025년 1월 7일 AM 10:39 UTCresolved

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

1. 2024년 12월 23일 AM 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. 2024년 12월 24일 PM 1: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. 2024년 12월 24일 PM 4:20 UTCresolved

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

1. 2024년 12월 3일 AM 7:48 UTCinvestigating

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

2. 2024년 12월 3일 AM 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. 2024년 12월 9일 PM 4:07 UTCresolved

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

1. 2024년 11월 13일 PM 5: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. 2024년 11월 13일 PM 7:09 UTCresolved

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

1. 2024년 8월 7일 PM 7: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. 2024년 8월 7일 PM 8:29 UTCresolved

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

1. 2024년 7월 29일 PM 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. 2024년 7월 29일 PM 12:10 UTCresolved

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