Avanan outage on May 3 22h 35m disruption
May 2, 11:13 PM → May 3, 09:48 PM · 22h 35m · high
Avanan experienced a service disruption, which was detected through user reports. The incident began on May 2, 2026, at 23:13 UTC and was resolved on May 3, 2026, at 21:48 UTC, lasting approximately 22 hours and 35 minutes.
Impact
Users reported a high severity disruption to Avanan services. The incident generated 764 total reports, with the predominant issue type being slow or unresponsive service, accounting for 736 reports. Other reported issues included email functionality problems and API access difficulties. No specific regional impact was recorded during this incident.
Top reported issues
- Slow / unresponsive736
- Email issues19
- API issues9
Incident timeline
- May 2, 11:13 PM
PulseWatch detected elevated report volume (high severity)
- May 3, 01:52 AM
Status updated: major issue
- May 3, 01:57 AM
Status updated: major issue
- May 3, 02:07 AM
Status updated: major issue
- May 3, 02:13 AM
Status updated: major issue
- May 3, 02:22 AM
Status updated: major issue
- May 3, 02:27 AM
Status updated: major issue
- May 3, 02:38 AM
Status updated: major issue
- May 3, 02:42 AM
Status updated: major issue
- May 3, 02:52 AM
Status updated: major issue
- May 3, 02:57 AM
Status updated: major issue
- May 3, 03:07 AM
Status updated: major issue
- May 3, 03:13 AM
Status updated: major issue
- May 3, 03:23 AM
Status updated: major issue
- May 3, 03:27 AM
Status updated: major issue
- May 3, 03:37 AM
Status updated: major issue
- May 3, 03:42 AM
Status updated: major issue
- May 3, 03:52 AM
Status updated: major issue
- May 3, 03:57 AM
Status updated: major issue
- May 3, 04:08 AM
Status updated: major issue
- May 3, 04:12 AM
Status updated: major issue
- May 3, 04:22 AM
Status updated: major issue
- May 3, 04:27 AM
Status updated: major issue
- May 3, 04:37 AM
Status updated: major issue
- May 3, 04:42 AM
Status updated: major issue
- May 3, 04:53 AM
Status updated: major issue
- May 3, 04:57 AM
Status updated: major issue
- May 3, 05:08 AM
Status updated: major issue
- May 3, 05:13 AM
Status updated: major issue
- May 3, 05:22 AM
Status updated: major issue
- May 3, 05:27 AM
Status updated: major issue
- May 3, 05:37 AM
Status updated: major issue
- May 3, 05:43 AM
Status updated: major issue
- May 3, 05:52 AM
Status updated: major issue
- May 3, 05:57 AM
Status updated: major issue
- May 3, 06:07 AM
Status updated: major issue
- May 3, 06:12 AM
Status updated: major issue
- May 3, 06:22 AM
Status updated: major issue
- May 3, 06:27 AM
Status updated: major issue
- May 3, 06:37 AM
Status updated: major issue
- May 3, 06:42 AM
Status updated: major issue
- May 3, 06:52 AM
Status updated: major issue
- May 3, 06:57 AM
Status updated: major issue
- May 3, 07:07 AM
Status updated: major issue
- May 3, 07:12 AM
Status updated: major issue
- May 3, 07:22 AM
Status updated: major issue
- May 3, 07:27 AM
Status updated: major issue
- May 3, 07:37 AM
Status updated: major issue
- May 3, 07:42 AM
Status updated: major issue
- May 3, 04:00 PM
Peak of 17 reports in 15 minutes (baseline 1.3)
- May 3, 09:37 PM
Status updated: major issue
- May 3, 09:42 PM
Status updated: major issue
- May 3, 09:48 PM
Report volume returned to baseline — incident resolved
Official updates
- May 2, 11:13 PM
Avanan status page acknowledged the incident.
View official source