- Detected by Pingoru
- Apr 23, 2026, 07:36 PM UTC
- Resolved
- Apr 23, 2026, 11:25 PM UTC
- Duration
- 3h 49m
Affected: Analytics - North America (NA)
Timeline · 3 updates
-
identified Apr 23, 2026, 07:36 PM UTC
We’re investigating an issue in Production (NA) where historical reporting does not display data as expected. We’re working to confirm the scope, identify the cause, and restore normal behavior. Updates will be posted here as we learn more.
-
monitoring Apr 23, 2026, 08:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 23, 2026, 11:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 10:06 AM UTC
- Resolved
- Mar 27, 2026, 08:06 AM UTC
- Duration
- 22h
Affected: Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)
Timeline · 3 updates
-
investigating Mar 26, 2026, 10:06 AM UTC
We are currently investigating an incident. Agents become stuck in status and cannot continue work. The AXP client becomes unresponsive, and agents are unable to: make outbound calls accept inbound calls receive new interactions log out or reset status Inbound calls are not being accepted by agents and are resulting in RONA. This is a service-level issue affecting the multiple agent population. Our teams are actively working to identify the root cause and restore service as quickly as possible. We will provide further updates as more information becomes available.
-
monitoring Mar 26, 2026, 11:18 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 27, 2026, 08:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 10:59 PM UTC
- Resolved
- Mar 20, 2026, 01:27 PM UTC
- Duration
- 14h 28m
Affected: Analytics - North America (NA)
Timeline · 3 updates
-
investigating Mar 19, 2026, 10:59 PM UTC
Historical reporting is not showing up data since 00:00 AM Mar 19.
-
monitoring Mar 20, 2026, 06:39 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 20, 2026, 01:27 PM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 12:39 AM UTC
- Resolved
- Mar 18, 2026, 12:17 PM UTC
- Duration
- 11h 37m
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)
Timeline · 4 updates
-
investigating Mar 18, 2026, 12:39 AM UTC
We are currently investigating the issue.
-
identified Mar 18, 2026, 02:08 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 18, 2026, 02:09 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 18, 2026, 12:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 12:07 AM UTC
- Resolved
- Mar 18, 2026, 12:28 AM UTC
- Duration
- 19d
Affected: Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)Analytics - United Kingdom (UK)Social Connections - United Kingdom (UK)API Access - United Kingdom (UK)Preview Dialing - United Kingdom (UK)
Timeline · 4 updates
-
investigating Feb 27, 2026, 12:07 AM UTC
We are currently investigating this issue.
-
identified Feb 27, 2026, 02:00 AM UTC
a fix and testing is in progress. The next update expected at 1pm GMT.
-
identified Mar 03, 2026, 11:43 AM UTC
We are currently experiencing technical difficulties with the service responsible for processing customer journey data. This is due to an issue with one of our infrastructure partners. Our team is working closely with the provider to resolve this as quickly as possible.
-
resolved Mar 18, 2026, 12:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 05:28 PM UTC
- Resolved
- Feb 20, 2026, 06:47 PM UTC
- Duration
- 1d 1h
Timeline · 3 updates
-
investigating Feb 19, 2026, 05:28 PM UTC
It is Impacting AXP Public customers in Prod-NA
-
monitoring Feb 20, 2026, 08:32 AM UTC
The patch has been rolled back by the vendor. We are currently monitoring the system and will share further updates as needed
-
resolved Feb 20, 2026, 06:47 PM UTC
Issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 07:02 PM UTC
- Resolved
- Feb 03, 2026, 08:25 PM UTC
- Duration
- 1h 22m
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)
Timeline · 3 updates
-
identified Feb 03, 2026, 07:02 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 03, 2026, 07:06 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 03, 2026, 08:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 08:53 AM UTC
- Resolved
- Feb 03, 2026, 12:13 PM UTC
- Duration
- 3h 20m
Timeline · 3 updates
-
investigating Feb 03, 2026, 08:53 AM UTC
Some users may experience issues while updating their profiles or during new user login attempts.
-
monitoring Feb 03, 2026, 09:29 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 03, 2026, 12:13 PM UTC
Incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 12:03 PM UTC
- Resolved
- Jan 30, 2026, 08:21 AM UTC
- Duration
- 20h 18m
Affected: Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)
Timeline · 5 updates
-
investigating Jan 29, 2026, 12:03 PM UTC
We are currently experiencing a feature degradation affecting delivery logic in the Prod-UK environment. Specifically, agents may receive multiple interactions despite multiplicity settings being restricted to 1. Our engineering team has identified the cause and is working toward an immediate resolution. We will keep you posted on the latest.
-
monitoring Jan 29, 2026, 01:52 PM UTC
We are monitoring the issue now
-
investigating Jan 29, 2026, 04:47 PM UTC
We are currently investigating this issue.
-
monitoring Jan 29, 2026, 08:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 30, 2026, 08:21 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 12:04 PM UTC
- Resolved
- Jan 26, 2026, 04:31 PM UTC
- Duration
- 4h 27m
Affected: Email - United Kingdom (UK)
Timeline · 3 updates
-
investigating Jan 26, 2026, 12:04 PM UTC
We are currently investigating reports of degraded email performance originating from our prod-UK datacenter. Users may experience increased latency or intermittent delays in message delivery. Our engineering team working on restoring full service.
-
monitoring Jan 26, 2026, 01:16 PM UTC
All Email systems are now functional we are closely monitoring the service for the next several hours to ensure continued stability. Thank you for your patience while we resolved this matter.
-
resolved Jan 26, 2026, 04:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 17, 2026, 02:23 PM UTC
- Resolved
- Jan 23, 2026, 06:24 PM UTC
- Duration
- 6d 4h
Affected: Chat - United Kingdom (UK)
Timeline · 3 updates
-
investigating Jan 17, 2026, 02:23 PM UTC
We are currently investigating this issue.
-
monitoring Jan 17, 2026, 03:26 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 23, 2026, 06:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 09:43 PM UTC
- Resolved
- Dec 17, 2025, 08:03 AM UTC
- Duration
- 10h 20m
Affected: Chat - North America (NA)
Timeline · 3 updates
-
investigating Dec 16, 2025, 09:43 PM UTC
We are currently investigating this issue.
-
monitoring Dec 16, 2025, 10:46 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 17, 2025, 08:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 08:28 AM UTC
- Resolved
- Dec 16, 2025, 08:39 AM UTC
- Duration
- 10m
Affected: Analytics - United Kingdom (UK)
Timeline · 3 updates
-
identified Dec 16, 2025, 08:28 AM UTC
We are currently experiencing delays in the display of realtime data specifically for the Agent (ITD) producer. You may notice that recent data points for this specific agent are not populating in the dashboard. Impact: Limited to Agent (ITD) data only. Status: Realtime data for all other producers is displaying correctly and is unaffected. Cause: We have identified a processing backlog and are working to resolve it. Action: The engineering team is actively working to clear the lag and restore Realtime processing.
-
monitoring Dec 16, 2025, 08:35 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 16, 2025, 08:39 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 06:22 AM UTC
- Resolved
- Dec 15, 2025, 06:22 AM UTC
- Duration
- —
Affected: Analytics - Asiapacific (APAC)
Timeline · 1 update
-
resolved Dec 15, 2025, 06:22 AM UTC
Issue has been resolved already.
Read the full incident report →
Critical December 7, 2025 - Detected by Pingoru
- Dec 07, 2025, 09:36 PM UTC
- Resolved
- Dec 08, 2025, 04:30 PM UTC
- Duration
- 18h 53m
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)
Timeline · 3 updates
-
investigating Dec 07, 2025, 09:36 PM UTC
We are investigating issue currently
-
investigating Dec 08, 2025, 02:45 AM UTC
The issue may be workaround by unassigning the agent from their location within AXP Administration and then reassigning the agent to a default location.
-
resolved Dec 08, 2025, 04:30 PM UTC
The incident has been resolved and services are operating normally. Avaya will continue to monitor the situatio.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 05:51 PM UTC
- Resolved
- Dec 06, 2025, 07:56 AM UTC
- Duration
- 14h 4m
Affected: Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)Analytics - United Kingdom (UK)Social Connections - United Kingdom (UK)API Access - United Kingdom (UK)Preview Dialing - United Kingdom (UK)
Timeline · 4 updates
-
investigating Dec 05, 2025, 05:51 PM UTC
We are currently investigating an issue where agents are unable to log in to the AXP Workspaces in the Prod-UK environment.
-
identified Dec 05, 2025, 06:38 PM UTC
The issue has been identified.
-
monitoring Dec 05, 2025, 08:49 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 06, 2025, 07:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2025, 05:39 PM UTC
- Resolved
- Nov 28, 2025, 09:23 AM UTC
- Duration
- 15h 44m
Timeline · 3 updates
-
identified Nov 27, 2025, 05:39 PM UTC
We are currently investigating an issue where newly created agents are unable to log in to Workspaces. Our teams are monitoring the situation closely and working toward a resolution. Please note - This issue is limited to newly created agents; all existing agents and active sessions remain fully operational. Further updates will be provided as the situation progresses.
-
monitoring Nov 27, 2025, 05:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 28, 2025, 09:23 AM UTC
If a new user has been created in the last two weeks and the user was unable to login, it is recommended to follow the KB article today again. https://kb.avaya.com/kb/index?page=content&id=SOLN385689
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 08:39 PM UTC
- Resolved
- Dec 02, 2025, 06:32 PM UTC
- Duration
- 5d 21h
Affected: Voice - North America (NA)Voice - Europe (EU)Voice - United Kingdom (UK)Voice - AsiaPacific (APAC)
Timeline · 2 updates
-
identified Nov 26, 2025, 08:39 PM UTC
We have identified a critical issue in pre-General Availability (GA) builds of Chrome/Chromium version 143 (Beta, Dev, and Canary channels). These unreleased versions introduce severe voice-path latency, including noticeable delays and echo during use of our service. These browser builds are not stable and are not supported for production use. Action Required: - Please ensure you are using a stable, fully released version of Chrome/Chromium — version 142 or earlier. Note: - There is no impact to stable, GA versions of Chrome/Chromium. If you are already on a stable release, no action is needed, and you can continue using the service without concern.
-
resolved Dec 02, 2025, 06:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 01:46 PM UTC
- Resolved
- Nov 26, 2025, 07:37 AM UTC
- Duration
- 17h 50m
Affected: Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)
Timeline · 2 updates
-
investigating Nov 25, 2025, 01:46 PM UTC
Some of the Voice and Digital are currently impacted and may not reach the agent, as an investigation is in process.
-
resolved Nov 26, 2025, 07:37 AM UTC
We have identified and resolved the issue
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:01 PM UTC
- Resolved
- Nov 19, 2025, 01:46 PM UTC
- Duration
- 1d 1h
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)Analytics - North America (NA)Social Connections - North America (NA)API Access - North America (NA)Preview Dialing - North America (NA)Voice - Europe (EU)Email - Europe (EU)Chat - Europe (EU)Messaging - Europe (EU)Analytics - Europe (EU)Social Connections - Europe (EU)API Access - Europe (EU)Preview Dialing - Europe (EU)Voice - United Kingdom (UK)Email - United Kingdom (UK)Chat - United Kingdom (UK)Messaging - United Kingdom (UK)Analytics - United Kingdom (UK)Social Connections - United Kingdom (UK)API Access - United Kingdom (UK)Preview Dialing - United Kingdom (UK)Voice - AsiaPacific (APAC)Email - AsiaPacific (APAC)Chat - AsiaPacific (APAC)Messaging - AsiaPacific (APAC)Analytics - Asiapacific (APAC)Social Connections - AsiaPacific (APAC)API Access - AsiaPacific (APAC)Preview Dialing - AsiaPacific (APAC)Voice - Australia (ANZ)Email - Australia (ANZ)Chat - Australia (ANZ)Messaging - Australia (ANZ)Analytics - Australia (ANZ)Social Connections - Australia (ANZ)API Access - Australia (ANZ)Voice - Canada (CA)Email - Canada (CA)Chat - Canada (CA)Messaging - Canada (CA)Analytics - Canada (CA)API Access - Canada (CA)Voice - Japan (JP)Email - Japan (JP)Chat - Japan (JP)Messaging - Japan (JP)Analytics - Japan (JP)API Access - Japan (JP)Voice - India (IN)Email - India (IN)Chat - India (IN)Messaging - India (IN)Analytics - India (IN)
Timeline · 3 updates
-
investigating Nov 18, 2025, 12:01 PM UTC
We identified that the service impact was caused by an ongoing Cloudflare outage affecting global traffic routing. Our systems experienced intermittent failures in request handling and degraded performance during this period.
-
monitoring Nov 18, 2025, 02:53 PM UTC
Cloudflare has implemented a fix, and Avaya services are improving. Avaya is continuing to monitor services.
-
resolved Nov 19, 2025, 01:46 PM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 07:16 PM UTC
- Resolved
- Nov 03, 2025, 09:54 PM UTC
- Duration
- 2h 37m
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)
Timeline · 3 updates
-
identified Nov 03, 2025, 07:16 PM UTC
We have identified the issue on the workspace agent and our team is actively working on a fix.
-
monitoring Nov 03, 2025, 07:42 PM UTC
Monitoring is in progress. All services are currently performing as expected.
-
resolved Nov 03, 2025, 09:54 PM UTC
All services are fully operational, and normal functionality has been restored.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 05:53 AM UTC
- Resolved
- Oct 09, 2025, 05:53 AM UTC
- Duration
- —
Affected: Recordings
Timeline · 1 update
-
resolved Oct 09, 2025, 05:53 AM UTC
We observed the recording issue post Verint maintenance update on Prod-ASE. Problem was resolved post Certificate update. There was no Data loss in this process.
Read the full incident report →
- Detected by Pingoru
- Sep 12, 2025, 12:01 PM UTC
- Resolved
- Sep 12, 2025, 12:38 PM UTC
- Duration
- 37m
Affected: Analytics - North America (NA)
Timeline · 3 updates
-
investigating Sep 12, 2025, 12:01 PM UTC
Impact: Some customers may experience degraded performance in Historical Reporting within the Prod-NA environment (North America). Current Status: Our engineering team is actively investigating the issue. We will provide updates as more information becomes available. We appreciate your patience and will keep you posted on progress.
-
monitoring Sep 12, 2025, 12:16 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 12, 2025, 12:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2025, 05:28 PM UTC
- Resolved
- Sep 09, 2025, 06:13 PM UTC
- Duration
- 45m
Affected: Voice - North America (NA)Email - North America (NA)Chat - North America (NA)Messaging - North America (NA)Analytics - North America (NA)Social Connections - North America (NA)API Access - North America (NA)Preview Dialing - North America (NA)
Timeline · 3 updates
-
investigating Sep 09, 2025, 05:28 PM UTC
We are investigating a possible issue. During this time agents may experience delays in workspaces.
-
monitoring Sep 09, 2025, 05:51 PM UTC
Issue has been self-recovered, monitoring the results.
-
resolved Sep 09, 2025, 06:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 01:05 PM UTC
- Resolved
- Sep 08, 2025, 01:05 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 08, 2025, 01:05 PM UTC
We recently identified an intermittent issue that caused errors during the saving of Agents. This issue has now been fully resolved, and no further action is required.
Read the full incident report →
