Is AudioEye down?
Last checked 10m agoNo incidents right now.
AudioEye is operational right now. Last checked 10m ago; the most recent incident resolved 38d ago.
Real-time AudioEye status, recent outages, and incident history — pulled directly from AudioEye's official status page at https://status.audioeye.com every 5 minutes. Pingoru tracks 6 AudioEye services and has captured 3 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment AudioEye reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 2 updates
- identified · May 05, 2026, 11:42 PM UTC
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.
- resolved · May 06, 2026, 03:05 PM UTC
The historical reporting data used in the Trends (Beta) feature has been restored.
Latest: The historical reporting data used in the Trends (Beta) feature has been restored.
-
-
Timeline · 1 update
- resolved · May 02, 2026, 03:57 AM UTC
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.
Latest: 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 o…
-
- AudioEye Services
Timeline · 1 update
- resolved · Mar 20, 2026, 06:25 PM UTC
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.
Latest: 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 appro…
-
- Started May 05, 2026, 11:42 PM UTC · Resolved May 06, 2026, 03:05 PM UTC · 15h 22m
- Started May 02, 2026, 03:57 AM UTC · Resolved May 01, 2026, 05:30 PM UTC · —
- Degradation of Audioeye Services ResolvedStarted Mar 20, 2026, 06:25 PM UTC · Resolved Mar 20, 2026, 06:25 PM UTC · —