Aha! had 18 outages in the last 2 years totaling 29h 53m of downtime — averaging 0.7 incidents per month.
There were 18 Aha! outages since June 11, 2024 totaling 29h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some customers are experiencing slow performance accessing the Aha! Application. Engineering has identified the problem and is working towards a solution.
Engineering has temporarily disabled some reporting functionality.
This incident has been resolved.
Some Aha! customers experienced elevated error rates between 7:26 AM and 8:52 AM EST.
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.
The issue was fully resolved at 10:42 AM EST.
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.
Webhooks from integrations are being captured, but are experiencing delays in processing due to the same root cause.
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.
We are observing recovery of webhook and background job processing, but full resolution is expected to take some time. Engineering continues to monitor.
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.
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.
Aha! was not available for some customers for approximately 5 minutes. Service has been fully restored.
Aha! frontend assets are loading incorrectly. Engineering is aware and is currently solving the problem.
This incident has been resolved.
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.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
Feature cards are not showing up in the parking lots of the features board.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
Some customers may currently be experiencing slow performance within the Aha! Application. Engineering is aware and is working on the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
Elevated error rates were noticed in the Aha! application. Engineering deployed a fix and the system is behaving well again.
Some customers experienced an elevated error rate when sending webhooks to Aha!. The root cause has been identified and resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some customers may be having trouble accessing Aha!. Engineering is engaged and investigating.
Service has been restored.
Some customers are experiencing degraded performance and occasional partial outages.
Partial outages have resolved. Some customers are still experiencing degraded performance.
This incident has been resolved with permanent fixes applied.
Aha! is not responding for some users. We are working on resolving the problem.
Some customers may have experienced slow response times during a three minute window. The root cause has been identified and resolved.