Avanan outage on May 2 — 1 day, 11 hour disruption
May 2, 10:28 AM → May 3, 10:18 PM · 1d 11h · high
On May 2, 2026, users reported an outage affecting the Avanan service. This disruption was detected through a significant increase in user reports. The incident was resolved on May 3, 2026.
Impact
During the incident, users primarily reported issues with the Avanan service being slow or unresponsive, accounting for 963 out of 1000 total reports. A smaller number of users also experienced email issues (19 reports) and API issues (18 reports). The outage was detected by PulseWatch following a surge in user reports, with a peak of 17 reports in a 15-minute period. No specific regional impact was recorded during this time.
Top reported issues
- Slow / unresponsive963
- Email issues19
- API issues18
Incident timeline
- May 2, 10:28 AM
PulseWatch detected elevated report volume (high severity)
- May 2, 11:52 AM
Status updated: major issue
- May 2, 11:57 AM
Status updated: major issue
- May 2, 12:07 PM
Status updated: major issue
- May 2, 12:12 PM
Status updated: major issue
- May 2, 12:22 PM
Status updated: major issue
- May 2, 12:27 PM
Status updated: major issue
- May 2, 12:38 PM
Status updated: major issue
- May 2, 12:42 PM
Status updated: major issue
- May 2, 12:52 PM
Status updated: major issue
- May 2, 12:57 PM
Status updated: major issue
- May 2, 01:07 PM
Status updated: major issue
- May 2, 01:12 PM
Status updated: major issue
- May 2, 01:22 PM
Status updated: major issue
- May 2, 01:27 PM
Status updated: major issue
- May 2, 01:37 PM
Status updated: major issue
- May 2, 01:42 PM
Status updated: major issue
- May 2, 01:52 PM
Status updated: major issue
- May 2, 01:58 PM
Status updated: major issue
- May 2, 02:07 PM
Status updated: major issue
- May 2, 02:12 PM
Status updated: major issue
- May 2, 02:22 PM
Status updated: major issue
- May 2, 02:27 PM
Status updated: major issue
- May 2, 02:37 PM
Status updated: major issue
- May 2, 02:42 PM
Status updated: major issue
- May 2, 02:52 PM
Status updated: major issue
- May 2, 02:57 PM
Status updated: major issue
- May 2, 03:07 PM
Status updated: major issue
- May 2, 03:12 PM
Status updated: major issue
- May 2, 03:22 PM
Status updated: major issue
- May 2, 03:27 PM
Status updated: major issue
- May 2, 03:37 PM
Status updated: major issue
- May 2, 03:42 PM
Status updated: major issue
- May 2, 03:52 PM
Status updated: major issue
- May 2, 03:57 PM
Status updated: major issue
- May 2, 04:07 PM
Status updated: major issue
- May 2, 04:12 PM
Status updated: major issue
- May 2, 04:22 PM
Status updated: major issue
- May 2, 04:27 PM
Status updated: major issue
- May 2, 04:37 PM
Status updated: major issue
- May 2, 04:43 PM
Status updated: major issue
- May 2, 04:52 PM
Status updated: major issue
- May 2, 04:58 PM
Status updated: major issue
- May 2, 05:07 PM
Status updated: major issue
- May 2, 05:13 PM
Status updated: major issue
- May 2, 05:23 PM
Status updated: major issue
- May 2, 05:28 PM
Status updated: major issue
- May 2, 05:37 PM
Status updated: major issue
- May 2, 05:43 PM
Status updated: major issue
- May 3, 04:00 PM
Peak of 17 reports in 15 minutes (baseline 1.3)
- May 3, 10:08 PM
Status updated: major issue
- May 3, 10:12 PM
Status updated: major issue
- May 3, 10:18 PM
Report volume returned to baseline — incident resolved
Official updates
- May 2, 10:28 AM
Avanan status page acknowledged the incident.
View official source