AudioEye incident

Degradation of Audioeye Services

Resolved after 8 minutes, affecting AudioEye Services, on March 20, 2026.

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.

Started
Mar 20, 2026, 05:56 PM UTC
Resolved
Mar 20, 2026, 06:04 PM UTC
Duration
8m
Detected by Pingoru
Mar 20, 2026, 05:56 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.

Your product runs on more than AudioEye

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →