AudioEye Outage History
6 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AudioEye Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PHP security vulnerabilitiesOn October 21, the PHP project disclosed two critical security vulnerabilities. One AudioEye service uses PHP, and we’ve updated it to a patched version. We’ve found no evidence of exploitation, and no action is needed… | 0 min | Resolved |
| Oct 21, 2026 | Historical Reporting & Dashboard Trends - Database MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 5, 2026 | Historical Reporting Data Temporarily UnavailableThe historical reporting data used in the Trends (Beta) feature has been restored. | 15h 22m | Resolved |
| May 2, 2026 | Brief DNS Disruption on Aegis Domains During Springtime MigrationDuring 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… | -627 min | Resolved |
| Mar 20, 2026 | Degradation of Audioeye ServicesDuring 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… | 0 min | Resolved |
| Feb 27, 2026 | JavaScript Freezing Client WebsitesThis incident has been resolved. | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next AudioEye incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This AudioEye Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AudioEye acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single AudioEye outage in this window ran 15h 22m, against a mean recovery of 3h 28m. If you depend on AudioEye in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.