Aha!

Affected: Aha! Builder applications

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-01 18:23 UTC

   Some Aha! Builder preview applications are temporarily unavailable. Aha! engineering has identified the problem and is working on a solution.

2. resolved 2026-10-01 18:56 UTC

   Resolution is confirmed. If you are still experiencing issues, try restarting your browser to clear stale DNS cache entries.

Excerpts are shortened. Read the full incident on Aha!'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 medium confidence (taxonomy v0.2).

1. resolved 2026-08-27 15:30 UTC

   Some users may have experienced slow performance for ten minutes between 8:27am and 8:37am PDT.

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

Affected: Aha! application

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 medium confidence (taxonomy v0.2).

1. monitoring 2026-07-28 13:36 UTC

   Performance for some customers was degraded between 8:45 AM EST and 9:32 AM EST. Aha! Engineering has applied mitigations, and performance is now nominal. Engineering continues to monitor.

2. monitoring 2026-07-28 14:00 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-07-28 14:25 UTC

   This incident has been resolved.

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

Affected: Aha! application

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 2026-02-18 13:51 UTC

   Some customers are experiencing slow performance accessing the Aha! Application. Engineering has identified the problem and is working towards a solution.

2. identified 2026-02-18 14:20 UTC

   Engineering has temporarily disabled some reporting functionality.

3. resolved 2026-02-18 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2026-02-10 14:30 UTC

   Some Aha! customers experienced elevated error rates between 7:26 AM and 8:52 AM EST.

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

Affected: Aha! application

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. monitoring 2026-02-03 15:03 UTC

   Some customers would have experienced slow performance this morning from 9:07 AM EST until 10:02 AM EST. Aha! Engineering has implemented a fix and is continuing to monitor.

2. resolved 2026-02-03 19:06 UTC

   The issue was fully resolved at 10:42 AM EST.

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

Affected: Aha! application, Webhook processing

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

Names an upstream provider: AWS.

1. identified 2025-10-20 14:18 UTC

   The AI Assistant and Email Deliverability are both experiencing degraded performance as a result of a widespread AWS outage. Aha! engineering is monitoring the situation and working to restore quality of service.

2. identified 2025-10-20 14:24 UTC

   Webhooks from integrations are being captured, but are experiencing delays in processing due to the same root cause.

3. identified 2025-10-20 16:10 UTC

   We are continuing to monitor the underlying incident with AWS, and are noting failures in background job processing as well. Engineering is continuing to work to ensure quality of service.

4. identified 2025-10-20 19:01 UTC

   We are observing recovery of webhook and background job processing, but full resolution is expected to take some time. Engineering continues to monitor.

5. monitoring 2025-10-20 21:06 UTC

   Background job processing and other functions are almost fully recovered. Aha! Engineering is continuing to monitor the system and make changes necessary to restore full functionality.

6. resolved 2025-10-20 22:16 UTC

   All Aha! functions have fully recovered, and we are currently processing through a backlog of asynchronous jobs. AWS is reporting that their incident has largely resolved, and Aha! is not affected by the few remaining services which are still degraded.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2025-09-11 03:50 UTC

   Aha! was not available for some customers for approximately 5 minutes. Service has been fully restored.

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

Affected: Aha! application

Failure mode: CDN or edge layer failed or served bad content. 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-07-23 02:49 UTC

   Aha! frontend assets are loading incorrectly. Engineering is aware and is currently solving the problem.

2. resolved 2025-07-23 02:51 UTC

   This incident has been resolved.

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

Affected: Aha! application

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-29 02:51 UTC

   Some search results are not available for certain customers. The issue has been identified and results will be available in the next few hours. ETA is 2025-06-29 at 06:00 UTC.

2. identified 2025-06-29 05:33 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2025-06-29 06:55 UTC

   This incident has been resolved.

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

Affected: Aha! application

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-06-20 17:29 UTC

   We are currently investigating this issue.

2. investigating 2025-06-20 17:30 UTC

   We are continuing to investigate this issue.

3. resolved 2025-06-20 17:34 UTC

   This incident has been resolved.

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

Affected: Aha! application

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-06-11 14:34 UTC

   Feature cards are not showing up in the parking lots of the features board.

2. identified 2025-06-11 14:34 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-06-11 14:36 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2025-06-11 14:56 UTC

   We are continuing to work on a fix for this issue.

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

Affected: Aha! application, Webhook processing

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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-06-04 15:50 UTC

   Some customers may currently be experiencing slow performance within the Aha! Application. Engineering is aware and is working on the issue.

2. monitoring 2025-06-04 16:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-04 16:40 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

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 medium confidence (taxonomy v0.2).

1. resolved 2025-04-08 02:15 UTC

   Some customers experienced elevated error rates when attempting to access the Aha! application between 10:06 and 10:11 PM EST. The errors have been resolved.

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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-12-25 14:00 UTC

   Elevated error rates were noticed in the Aha! application. Engineering deployed a fix and the system is behaving well again.

Excerpts are shortened. Read the full incident on Aha!'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 medium confidence (taxonomy v0.2).

1. resolved 2024-11-11 19:00 UTC

   Some customers experienced an elevated error rate when sending webhooks to Aha!. The root cause has been identified and resolved.

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

Affected: Aha! application

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-11-08 14:48 UTC

   We are currently investigating this issue.

2. identified 2024-11-08 14:57 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-11-08 14:58 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-11-08 15:15 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

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-10-30 00:26 UTC

   Some customers may be having trouble accessing Aha!. Engineering is engaged and investigating.

2. resolved 2024-10-30 00:29 UTC

   Service has been restored.

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

Affected: Aha! application, Webhook processing

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-10-07 15:00 UTC

   Some customers are experiencing degraded performance and occasional partial outages.

2. monitoring 2024-10-07 18:21 UTC

   Partial outages have resolved. Some customers are still experiencing degraded performance.

3. resolved 2024-10-08 02:00 UTC

   This incident has been resolved with permanent fixes applied.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2024-09-28 15:00 UTC

   Aha! is not responding for some users. We are working on resolving the problem.

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

Affected: Aha! application

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-23 20:34 UTC

   We are currently investigating this issue.

2. identified 2024-07-23 20:41 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-07-23 20:42 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-07-23 20:46 UTC

   This incident has been resolved.

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

Affected: Aha! application

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-15 14:11 UTC

   Engineering is investigating elevated error rates and degraded performance for some customers.

2. monitoring 2024-07-15 14:47 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-07-15 21:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2024-06-11 02:15 UTC

   Some customers may have experienced slow response times during a three minute window. The root cause has been identified and resolved.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-05-24 17:27 UTC

   Some customers experienced elevated error rates in DNS resolution for a five-minute period between 1:27 PM EST and 1:32 PM EST.

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

Affected: Aha! application, Webhook processing

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-02-27 13:30 UTC

   We are investigating a problem where some users are seeing very slow performance or the inability to reach Aha!

2. identified 2024-02-27 14:26 UTC

   Access to Aha! has been restored for all users.

3. identified 2024-02-27 14:36 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2024-02-27 14:55 UTC

   The issue is resolved for all users. We are monitoring the system.

5. resolved 2024-02-27 19:54 UTC

   This incident has been resolved.

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

Affected: Aha! application

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. identified 2023-11-08 14:54 UTC

   A major outage at a sub-processor has disabled the "Draft with AI" and other features which leverage generative AI. AI-powered Idea explorations are not affected. Aha! Engineering is monitoring the sub-processor's outage and will update as their service recovers.

2. resolved 2023-11-08 16:21 UTC

   Our sub-processor has resolved their outage, and generative AI features are working again.

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

Affected: Aha! application

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 medium confidence (taxonomy v0.2).

1. resolved 2023-09-29 14:21 UTC

   Engineering observed elevated error rates for the Aha! Editor, whiteboard, and presentations. Engineering has taken action to resolve the errors, and these components should now be working again after a browser refresh.

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

Affected: Aha! application

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. monitoring 2023-08-24 18:10 UTC

   Customers using the EU data center may have seen trouble loading some pages in Aha! or general slow performance.

2. resolved 2023-08-24 18:34 UTC

   Performance has now returned to normal.

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

Affected: Aha! application, Webhook processing

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 2023-03-30 01:30 UTC

   Aha! is not responding for some users. We are working on resolving the problem.

2. identified 2023-03-30 01:38 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2023-03-30 01:47 UTC

   The problem has been resolved.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2022-12-21 23:41 UTC

   We experienced a problem with webhooks today for a short period of time. The issue has been resolved and they are working normally. However, between 13:08 PST and 15:41 PST changes from incoming webhooks were not processed and some outgoing updates failed to be sent. This means...

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

Affected: Aha! application, Webhook processing

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. monitoring 2022-11-15 16:28 UTC

   We have seen slow performance for some customers over the last 15 minutes. Performance is back to normal now. We are investigating the cause.

2. monitoring 2022-11-15 16:48 UTC

   We are continuing to monitor for any further issues.

3. resolved 2022-11-15 16:48 UTC

   This incident has been resolved.

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

Affected: Aha! application

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 2022-09-02 04:00 UTC

   For some customers it is not possible to search for records inside Aha! using the full-text search dialog. We are working on resolving the problem and expect it to be fixed at about 12:00pm UTC on Friday.

2. identified 2022-09-02 08:16 UTC

   We are continuing to work on a fix for this issue.

3. identified 2022-09-02 11:23 UTC

   Searching for records inside Aha! using the full-text search dialog has been fully restored.

4. resolved 2022-09-02 14:23 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

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. resolved 2022-08-20 03:02 UTC

   Between 19:15 and 19:40 PDT the creation and deletion of some types of records may have failed for some accounts. The root cause is now resolved.

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

Affected: Aha! application

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2022-03-22 22:17 UTC

   Aha! Engineering is aware of slow response time for the Aha! application for some customers within a single data center. Engineering is actively working on resolving the problem now.

2. resolved 2022-03-22 23:02 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

Failure mode: A zone, region or data center became unavailable. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2022-03-10 19:05 UTC

   Aha! Experienced a momentary loss of connectivity in one data center, affecting some customers. Connectivity recovered soon afterwards. Aha! Engineering has discovered the root cause and does not expect the problem to recur.

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

Affected: Aha! application

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 medium confidence (taxonomy v0.2).

1. investigating 2022-03-02 18:55 UTC

   We are observing that some pages and descriptions are failing to load or update for users.

2. investigating 2022-03-02 20:09 UTC

   We are continuing to work on some slow performance. Editing descriptions should be working for all users. If you see any issues, reloading the page should fix them.

3. resolved 2022-03-02 20:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aha!'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 2022-03-01 15:29 UTC

   Users may not be receiving notifications or password reset emails from Aha! We are investigating the issue.

2. identified 2022-03-01 15:30 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2022-03-01 16:06 UTC

   This incident has been resolved.

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

Affected: Aha! application

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

Names an upstream provider: AWS.

1. identified 2021-12-07 17:05 UTC

   Aha! Engineering is aware of delayed processing for large background jobs, such as bulk imports and exports. This problem is caused by a widespread issue affecting the Amazon Web Services infrastructure used by Aha!. Aha! engineers are monitoring the situation and will provide...

2. monitoring 2021-12-07 21:51 UTC

   The Amazon Web Services infrastructure on which Aha! relies is beginning to recover. We are working through the backlog of large jobs now.

3. resolved 2021-12-07 22:30 UTC

   The back-log of jobs has been processed. Aha! engineering will continue to monitor the AWS outage to ensure no impact to other services.

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

Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2021-08-25 13:30 UTC

   Engineering became aware of slow application performance for all Aha! users as a result of a one-time operation. Engineering addressed the root cause, and performance has returned to normal.

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

Affected: Aha! application, Webhook processing

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 2021-07-17 14:13 UTC

   Aha! is currently not available. We are working on restoring service as quickly as possible. Please check here for updates.

2. investigating 2021-07-17 14:17 UTC

   Aha! is operational again.

3. resolved 2021-07-17 14:18 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

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 2021-01-27 16:16 UTC

   We are currently investigating.

2. resolved 2021-01-27 16:20 UTC

   The incident is resolved and Aha! is working for all users.

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

Affected: Aha! application

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 2021-01-07 15:15 UTC

   Aha! is currently not available. We are working on restoring service as quickly as possible. Please check here for updates.

2. resolved 2021-01-07 15:15 UTC

   This incident has been resolved.

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

Affected: Aha! application

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2020-12-16 03:15 UTC

   Ideas portals which are configured to use a custom CNAME are not returning the correct TLS certificate. We have confirmed the problem and are working on a fix.

2. resolved 2020-12-16 11:38 UTC

   The problem has been resolved. All ideas portals are now returning the correct certificate.

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

Affected: Aha! application

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 2020-10-09 19:42 UTC

   Aha! is currently not available for some users. We are working on restoring service as quickly as possible. Please check here for updates.

2. investigating 2020-10-09 19:44 UTC

   We are continuing to investigate this issue.

3. resolved 2020-10-09 19:44 UTC

   This incident has been resolved.

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

Affected: Aha! application

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 2020-09-24 19:35 UTC

   We are observing that some pages are failing to load for users. We are investigating the problem.

2. resolved 2020-09-24 19:50 UTC

   Performance has returned to normal.

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

Affected: Aha! application

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 2020-09-05 18:53 UTC

   Aha! is currently not available for some users. We are working on restoring service as quickly as possible. Please check here for updates.

2. resolved 2020-09-05 18:56 UTC

   This incident has been resolved.

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

Affected: Aha! application, Webhook processing

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 2020-08-04 14:02 UTC

   We are currently investigating this issue.

2. resolved 2020-08-04 14:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Aha!'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. resolved 2020-07-14 10:30 UTC

   Some users are reporting problems creating new records. The problem is now fixed.

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

Affected: Aha! application

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2020-05-11 21:30 UTC

   Some customers are experiencing problems logging in to Aha! using SAML SSO. We have identified the problem and are working on a fix now.

2. resolved 2020-05-11 22:04 UTC

   The problem is resolved and SAML logins are working again.

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

Affected: Aha! application

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 2020-04-15 20:36 UTC

   Aha! is currently not available. We are working on restoring service as quickly as possible. Please check here for updates.

2. resolved 2020-04-15 20:39 UTC

   This incident has been resolved.

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