AudioEye incident

Degradation of Audioeye Services

Notice Resolved View vendor source →
Started
Mar 20, 2026, 06:25 PM UTC
Resolved
Mar 20, 2026, 06:25 PM UTC
Duration
Detected by Pingoru
Mar 20, 2026, 06:25 PM UTC

Affected components

AudioEye Services

Update timeline

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

Looking to track AudioEye downtime and outages?

Pingoru polls AudioEye's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when AudioEye reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track AudioEye alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring AudioEye for free

5 free monitors · No credit card required