Avaya Outage History

Avaya's Production North America datacenter experienced a major incident where historical reporting failed to display data properly, affecting the Analytics component for the NA region. The issue lasted 3.9 hours before a fix was implemented and monitored for stability. The incident was fully resolved with normal reporting functionality restored.

Avaya's AX Public service in the UK data center experienced a major incident where agents became stuck in status with unresponsive AXP clients, preventing them from making or accepting calls, receiving interactions, or logging out, which caused inbound calls to result in RONA (Ring On No Answer). The incident affected all communication channels including voice, email, chat, and messaging across the UK region for 22.1 hours before being resolved with an implemented fix.

Avaya's historical reporting system in North America stopped displaying data starting at midnight on March 19, affecting the Analytics component. A fix was implemented and the incident was resolved after 14.5 hours of monitoring to ensure the reporting data was restored properly.

Avaya Workspaces agents in North America were unable to change their status to "Go Ready" state, affecting voice, email, chat, and messaging services. The issue was identified and a fix was implemented after investigation. The incident was resolved after 11.7 hours of service disruption.

Avaya's UK production environment experienced ongoing instability with the AXP Customer Journey service, affecting all major communication channels including voice, email, chat, messaging, analytics, social connections, API access, and preview dialing. The issue was caused by problems with an infrastructure partner and persisted for approximately 19 days before being resolved. The incident was successfully fixed after collaborative work between Avaya's team and the third-party provider.