Attio Outage History

Attio is up right now

Attio had 6 outages in the last 2 years totaling 21h 29m of downtime — averaging 0.2 incidents per month.

There were 6 Attio outages since October 30, 2025 totaling 21h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.attio.com

Minor July 23, 2026

Failures triggering workflow runs

Detected by Pingoru
Jul 23, 2026, 05:29 PM UTC
Resolved
Jul 23, 2026, 05:29 PM UTC
Duration
Affected: Attio Cloud
Timeline · 5 updates
  1. investigating Jul 21, 2026, 05:35 PM UTC

    Status: Investigating 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. Affected components Attio Cloud (Partial outage)

  2. identified Jul 21, 2026, 05:39 PM UTC

    Status: Identified 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. Affected components Attio Cloud (Partial outage)

  3. monitoring Jul 21, 2026, 06:00 PM UTC

    Status: Monitoring Our team has deployed a fix for the issue and are currently monitoring the system to ensure the issue is resolved. Affected components Attio Cloud (Operational)

  4. monitoring Jul 21, 2026, 08:19 PM UTC

    Status: Monitoring 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 workflow triggers not run properly. What we did: We reverted the change and corrected the underlying infrastructure configuration. All impacted workflow triggers resumed processing normally by 18:01 UTC, and we've since confirmed triggers are operating correctly. We’re continuing to investigate recovering runs triggered during this timeframe. We’ll update this page as soon as we have an update. Affected components Attio Cloud (Operational)

  5. resolved Jul 23, 2026, 05:29 PM UTC

    Status: Resolved 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. Affected components Attio Cloud (Operational)

Read the full incident report →

Minor July 10, 2026

Intimitent errors across some platform features

Detected by Pingoru
Jul 10, 2026, 07:26 PM UTC
Resolved
Jul 10, 2026, 07:26 PM UTC
Duration
Affected: Attio Web Client
Timeline · 3 updates
  1. investigating Jul 10, 2026, 05:19 PM UTC

    Status: Investigating 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. Affected components Attio Web Client (Degraded performance)

  2. identified Jul 10, 2026, 05:36 PM UTC

    Status: Identified We've identified the issue caused by an upstream provider - our team is working to mitigate the issue as quickly as possible. Affected components Attio Web Client (Degraded performance)

  3. resolved Jul 10, 2026, 07:26 PM UTC

    Status: Resolved The issue has now been resolved. We apologize for any inconvenience caused. Affected components Attio Web Client (Operational)

Read the full incident report →

Minor June 19, 2026

Issues accessing email content, call recordings, uploads, and exports.

Detected by Pingoru
Jun 19, 2026, 01:06 PM UTC
Resolved
Jun 19, 2026, 01:06 PM UTC
Duration
Timeline · 3 updates
  1. identified Jun 19, 2026, 10:43 AM UTC

    Status: Identified 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 Jun 19, 2026, 10:56 AM UTC

    Status: Monitoring 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 Jun 19, 2026, 01:06 PM UTC

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

Read the full incident report →