AudioEye had 6 outages in the last 2 years totaling 19h 42m of downtime — averaging 0.2 incidents per month.
There were 6 AudioEye outages since September 11, 2024 totaling 19h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are aware of an issue affecting historical reporting data in our Trends (Beta) feature and are actively working to restore it. This does not affect live site scanning or accessibility monitoring. We will post updates as restoration progresses.
The historical reporting data used in the Trends (Beta) feature has been restored.
During a planned migration of the Springtime CMP toolbar to new infrastructure, the aegis.audioeye.com and aegis.audioeye-services.com domains experienced approximately 4 minutes of DNS unavailability while DNS records were manually transferred to a new Cloudflare Pages deployment. Service was restored once the DNS update completed, and no further impact was observed.
During a scheduled deployment of CDN rules, we unintentionally triggered a cache purge. The resulting traffic spike overwhelmed our backend systems, causing server errors for approximately 0.5% of requests between 17:56–18:04 UTC. Our on-call team detected the issue within minutes and restored capacity by scaling backend resources.
This incident has been resolved.
We are investigating reports of broken links and SSO failures on the audioeye portal. A rollback is being initiated.
Fixes have been applied and we are working on restoring remaining functionality.
We are continuing to investigate this issue. We are aware of intermittent issues with Partner authentication through portal.
The Audioeye Portal is now fully operational.
We are aware of an issue with AudioEye's Visual Toolkit styles being enabled regardless of user action on some sites. Our teams have identified the root cause and are working to correct the issue. At this time, we do not have an estimated time of resolution. We will share updates once we know more, and we apologize for any inconvenience this may be causing you or your customers.
We are continuing to work on a fix for this issue.
A fix has been implemented and this issue is now resolved.