Attio

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-06 23:14 UTC

   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. resolved 2026-10-12 08:58 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 16:32 UTC

   We’re investigating reports of delays to formula attribute invalidations, our team is working to resolve the issue as quickly as possible.

2. identified 2026-10-06 20:49 UTC

   We have identified the cause of the delays to formula updates and are working through the backlog. Some formulas may continue to show outdated values until processing catches up.

3. monitoring 2026-10-06 22:13 UTC

   A fix has been applied and formula updates are processing normally again. The remaining backlog is catching up and we expect it to clear within the next hour.

4. resolved 2026-10-07 09:50 UTC

   The issue causing delays to formula updates has now been resolved, and the backlog has been fully processed. We're sorry for any inconvenience caused.

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-28 16:43 UTC

   We have identified an issue that is causing a delay to all workflow runs. We are working to resume processing as quickly as possible and apologise for any inconvenience caused.

2. identified 2026-09-28 17:46 UTC

   We are continuing to respond to an incident affecting workflow block execution and webhook delivery.

3. identified 2026-09-28 20:09 UTC

   We are continuing to respond to issues with workflow execution and webhook delivery. We are also aware of potential impact to the import / export subsystems as well as Ask Attio. We are working to restore service availability.

4. resolved 2026-09-28 20:47 UTC

   The issue affecting workflow execution and webhook delivery has now been resolved. We’re sorry for any inconvenience caused.

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 17:05 UTC

   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. monitoring 2026-09-08 17:24 UTC

   Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

3. monitoring 2026-09-08 17:37 UTC

   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.

4. resolved 2026-09-08 18:42 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-21 17:35 UTC

   We're investigating reports of workflows failing to trigger. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. identified 2026-07-21 17:39 UTC

   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. monitoring 2026-07-21 18:00 UTC

   Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved.

4. monitoring 2026-07-21 20:19 UTC

   Between 16:33 and 18:01 UTC on July 21, 2026, some workflows failed to trigger correctly. **What happened:** An infrastructure configuration change deployed shortly before the incident caused an error when encrypting the content of newly received workflows, which caused some...

5. resolved 2026-07-23 17:29 UTC

   The issue has now been resolved and we have directly notified all customers who were impacted by this outage. We’re sorry for any inconvenience caused.

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-10 17:19 UTC

   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. identified 2026-07-10 17:36 UTC

   We've identified the issue caused by an upstream provider - our team is working to mitigate the issue as quickly as possible.

3. resolved 2026-07-10 19:26 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-19 10:43 UTC

   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. monitoring 2026-06-19 10:56 UTC

   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. resolved 2026-06-19 13:06 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-09 11:50 UTC

   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...

2. monitoring 2025-12-09 12:17 UTC

   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. resolved 2025-12-09 17:51 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 11:42 UTC

   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. identified 2025-11-18 11:44 UTC

   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. identified 2025-11-18 12:15 UTC

   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. monitoring 2025-11-18 14:57 UTC

   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. resolved 2025-11-18 21:47 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-30 11:56 UTC

   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...

2. monitoring 2025-10-30 16:43 UTC

   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. resolved 2025-10-30 17:19 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-29 17:37 UTC

   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. identified 2025-07-29 17:40 UTC

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

3. resolved 2025-07-29 22:19 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-16 18:49 UTC

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

2. resolved 2025-06-17 09:00 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:40 UTC

   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. identified 2025-06-12 19:18 UTC

   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...

3. monitoring 2025-06-12 19:36 UTC

   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. resolved 2025-06-12 20:56 UTC

   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.

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-02 22:55 UTC

   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. resolved 2025-06-03 15:39 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-24 14:17 UTC

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

2. monitoring 2025-04-24 14:21 UTC

   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. resolved 2025-04-24 15:06 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-04-19 15:34 UTC

   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. monitoring 2025-04-19 21:45 UTC

   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. resolved 2025-04-23 12:31 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-24 15:31 UTC

   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. identified 2025-03-24 15:36 UTC

   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. monitoring 2025-03-24 16:26 UTC

   Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is fully resolved.

4. resolved 2025-03-24 16:37 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-05 10:00 UTC

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

2. resolved 2025-01-07 10:39 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-12-23 11:54 UTC

   We are aware of an issue affecting the speed of CSV Imports. Our team are currently working to resolve the issue.

2. monitoring 2024-12-24 13:19 UTC

   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. resolved 2024-12-24 16:20 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-03 07:48 UTC

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

2. monitoring 2024-12-03 11:44 UTC

   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. resolved 2024-12-09 16:07 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-11-13 17:00 UTC

   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. resolved 2024-11-13 19:09 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-07 19:20 UTC

   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. resolved 2024-08-07 20:29 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-07-29 12:02 UTC

   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. resolved 2024-07-29 12:10 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-07-26 15:22 UTC

   We have identified an issue relating to the availability of the Attio Web application. We are working to restore access at this time.

2. resolved 2024-07-26 15:27 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-19 14:54 UTC

   We are investigating reports of issues loading Attio workspaces. We are currently investigating the root cause and our team is working to resolve the issue as quickly as possible.

2. monitoring 2024-07-19 15:12 UTC

   We are continuing to monitor the platform to ensure the stability of the service.

3. resolved 2024-07-29 12:09 UTC

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

Excerpts are shortened. Read the full incident on Attio's status page.