Skip to content
Back to AvananIncident Postmortem
Avanan logo

Avanan

Tracked by PulseWatch

Auto-drafted postmortem

Avanan outage on May 2 — 1d 4h disruption

May 2, 05:30 PM → May 3, 10:03 PM · 1d 4h · high

Avanan experienced a service disruption, detected through user reports. The incident began on May 2 and was resolved on May 3.

Peak reports
11
in 15 min
Total reports
965
during the incident
Duration
1d 4h
tracked by PulseWatch

Impact

Users reported experiencing issues with Avanan services. The primary reported issues included slow or unresponsive service, accounting for the majority of reports. A smaller number of users also reported email and API-related problems. No specific regional impact was recorded during the incident.

Top reported issues

  • Slow / unresponsive928
  • Email issues19
  • API issues18

Incident timeline

  1. May 2, 05:30 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 2, 05:52 PM

    Status updated: major issue

  3. May 2, 05:57 PM

    Status updated: major issue

  4. May 2, 06:07 PM

    Status updated: major issue

  5. May 2, 06:12 PM

    Status updated: major issue

  6. May 2, 06:22 PM

    Status updated: major issue

  7. May 2, 06:27 PM

    Status updated: major issue

  8. May 2, 06:38 PM

    Status updated: major issue

  9. May 2, 06:42 PM

    Status updated: major issue

  10. May 2, 06:52 PM

    Status updated: major issue

  11. May 2, 06:57 PM

    Status updated: major issue

  12. May 2, 07:07 PM

    Status updated: major issue

  13. May 2, 07:12 PM

    Status updated: major issue

  14. May 2, 07:22 PM

    Status updated: major issue

  15. May 2, 07:27 PM

    Status updated: major issue

  16. May 2, 07:37 PM

    Status updated: major issue

  17. May 2, 07:42 PM

    Status updated: major issue

  18. May 2, 07:53 PM

    Status updated: major issue

  19. May 2, 07:57 PM

    Status updated: major issue

  20. May 2, 08:07 PM

    Status updated: major issue

  21. May 2, 08:12 PM

    Status updated: major issue

  22. May 2, 08:22 PM

    Status updated: major issue

  23. May 2, 08:28 PM

    Status updated: major issue

  24. May 2, 08:37 PM

    Status updated: major issue

  25. May 2, 08:42 PM

    Status updated: major issue

  26. May 2, 08:52 PM

    Status updated: major issue

  27. May 2, 08:57 PM

    Status updated: major issue

  28. May 2, 09:07 PM

    Status updated: major issue

  29. May 2, 09:12 PM

    Status updated: major issue

  30. May 2, 09:22 PM

    Status updated: major issue

  31. May 2, 09:27 PM

    Status updated: major issue

  32. May 2, 09:37 PM

    Status updated: major issue

  33. May 2, 09:42 PM

    Status updated: major issue

  34. May 2, 09:52 PM

    Status updated: major issue

  35. May 2, 09:57 PM

    Status updated: major issue

  36. May 2, 10:07 PM

    Status updated: major issue

  37. May 2, 10:12 PM

    Status updated: major issue

  38. May 2, 10:22 PM

    Status updated: major issue

  39. May 2, 10:27 PM

    Status updated: major issue

  40. May 2, 10:37 PM

    Status updated: major issue

  41. May 2, 10:42 PM

    Status updated: major issue

  42. May 2, 10:52 PM

    Status updated: major issue

  43. May 2, 10:57 PM

    Status updated: major issue

  44. May 2, 11:07 PM

    Status updated: major issue

  45. May 2, 11:12 PM

    Status updated: major issue

  46. May 3, 04:00 PM

    Peak of 17 reports in 15 minutes (baseline 1.3)

  47. May 3, 09:52 PM

    Status updated: major issue

  48. May 3, 09:57 PM

    Status updated: major issue

  49. May 3, 10:03 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 05:30 PM

    Avanan status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash