- Detected by Pingoru
- Jun 03, 2026, 04:13 PM UTC
- Resolved
- Jun 03, 2026, 04:57 PM UTC
- Duration
- 43m
Affected: Americas (US East)Americas (US West)FedRAMP
Timeline · 2 updates
-
identified Jun 03, 2026, 04:13 PM UTC
We have identified an issue impacting users ability to playback voicemails. As a work around, customers can follow instructions in the linked https://help.genesys.cloud/articles/open-play-voicemail/ to add necessary permissions to resolve. Next update 12:45 PM Eastern or sooner.
-
resolved Jun 03, 2026, 04:57 PM UTC
Root cause was identified as an incomplete permissions backfill on a subset of organizations. The recommended workaround of manually adding the missing voicemail stream permissions as indicated in https://help.genesys.cloud/articles/open-play-voicemail/ is the permanent solution to backfilling the missing permissions. A formal RCA will be provided to those customers impacted by this issue.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 11:47 AM UTC
- Resolved
- May 19, 2026, 01:02 PM UTC
- Duration
- 1h 14m
Affected: EMEA (London)
Timeline · 4 updates
-
identified May 19, 2026, 11:47 AM UTC
We have identified an issue causing CoPilot Summaries to fail in the London region. Mitigation steps are being implemented. Next update 08:15 Eastern or sooner as information becomes available.
-
monitoring May 19, 2026, 12:08 PM UTC
Mitigation steps were successful and we are beginning to see improvement. Customers will continue to see impact until the backlogged events have been processed. Next update 08:45 Eastern or sooner as information becomes available.
-
monitoring May 19, 2026, 12:48 PM UTC
The backlogged events are continuing to be processed successfully. Customers will see impact to CoPilot Summaries until the backlog is fully clear. Next update 09:45 Eastern or sooner as information becomes available.
-
resolved May 19, 2026, 01:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 02:51 PM UTC
- Resolved
- May 08, 2026, 05:30 PM UTC
- Duration
- 2h 39m
Affected: Americas (US East)
Timeline · 5 updates
-
investigating May 08, 2026, 02:51 PM UTC
We are investigating an issue in the US-East region where interactions are being routed to unavailable agents. As teams work to restore, as a work around, customers can remove offline agents from the queue. Next update 11:30 Eastern
-
identified May 08, 2026, 03:34 PM UTC
Root cause has been identified. The engineering teams are actively evaluating mitigation strategies and we have engaged additional technical resources to expedite resolution. As a work around, customers can remove the offline agents from queues. Next update 12:30 Eastern or sooner as information becomes available.
-
identified May 08, 2026, 04:10 PM UTC
Teams have developed a fix and are actively testing before deploying to production. Next update 13:00 or sooner as information becomes available.
-
identified May 08, 2026, 04:40 PM UTC
The fix is now being deployed to production. We anticipate 20-30 minutes to complete. Next update 13:30 or sooner as information becomes available.
-
resolved May 08, 2026, 05:30 PM UTC
We have successfully resolved the agent routing issues. The service teams have cleared agents stuck in incorrect statuses, stopped routing interactions to offline agents, and restored real-time queue visibility.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:25 AM UTC
- Resolved
- May 08, 2026, 04:14 AM UTC
- Duration
- 2h 49m
Affected: Americas (US East)
Timeline · 5 updates
-
investigating May 08, 2026, 01:25 AM UTC
We are investigating an issue in the US East region that is impacting customers ability to route any interactions. This is impacting all interactions.
-
identified May 08, 2026, 02:04 AM UTC
Root cause has been identified and Genesys engineering teams are working with the platform provider to mitigate current impact. Next update bottom of the hour or as information becomes available.
-
identified May 08, 2026, 02:20 AM UTC
Teams have taken mitigation steps and are monitoring performance to see if there is improvement. Next update 10:45pm ET.
-
monitoring May 08, 2026, 02:37 AM UTC
Error rates have decreased and health checks have returned to normal. Monitoring for stability while the platform provider completes remaining mitigation steps.
-
resolved May 08, 2026, 04:14 AM UTC
All services are operational and traffic is routing successfully via a temporary workaround while the platform provider completes restoration. We will be performing a brief maintenance lasting approximately 30 minutes to restore original configurations.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 02:56 PM UTC
- Resolved
- Apr 22, 2026, 04:43 PM UTC
- Duration
- 1h 47m
Affected: Americas (US East)
Timeline · 5 updates
-
investigating Apr 22, 2026, 02:56 PM UTC
We are actively investigating an issue causing delays with all real time analytics data, including detail records, aggregate metrics, observation metrics and notifications. Next update 11:30 Eastern or sooner as information becomes available.
-
investigating Apr 22, 2026, 03:32 PM UTC
The service teams continue to actively investigate root cause of the issue causing delays in real-time analytics. Customers will continue to experience delays in detail records, aggregate metrics, observation metrics and notifications until resolution and backlogged events are cleared. Next update 12:15 Eastern or sooner as information becomes available.
-
monitoring Apr 22, 2026, 03:52 PM UTC
Mitigation steps have been implemented and we are beginning to see improvement. Users will continue to experience delays until the backlogged events have been completely processed. Next update 12:30 Eastern or sooner as information becomes available.
-
monitoring Apr 22, 2026, 04:34 PM UTC
We are seeing significant improvement now and the backlogged events continue to be processed. Customers will continue to see latency until the backlog is completely processed. Next update 13:30 or sooner as information becomes available.
-
resolved Apr 22, 2026, 04:43 PM UTC
The backlog has been completely processed and real time analytics is operating normally.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 08:34 PM UTC
- Resolved
- Mar 27, 2026, 09:01 PM UTC
- Duration
- 26m
Affected: Americas (Sao Paulo)Americas (US East)Asia Pacific (Sydney)
Timeline · 3 updates
-
investigating Mar 27, 2026, 08:34 PM UTC
Service teams are investigating an issue resulting in delays in realtime analytics data. Next update 17:00 Eastern or sooner as information becomes available.
-
investigating Mar 27, 2026, 08:47 PM UTC
Mitigation steps are being implemented and we are beginning to see improvement.
-
resolved Mar 27, 2026, 09:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 02:48 PM UTC
- Resolved
- Mar 24, 2026, 03:20 PM UTC
- Duration
- 31m
Affected: Asia Pacific (Seoul)
Timeline · 3 updates
-
investigating Mar 24, 2026, 02:48 PM UTC
Service teams are investigating an issue impacting ACD Email in the Seoul region.
-
monitoring Mar 24, 2026, 03:13 PM UTC
Mitigation steps have been implemented and the email backlog is being processed.
-
resolved Mar 24, 2026, 03:20 PM UTC
The email backlog processed and region is healthy. Incident Resolved
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:59 AM UTC
- Resolved
- Mar 12, 2026, 03:26 AM UTC
- Duration
- 26m
Affected: Asia Pacific (Sydney)
Timeline · 3 updates
-
investigating Mar 12, 2026, 02:59 AM UTC
Genesys teams are investigating an issue with the platform provider that is impacting copilot functionality, auto-summaries not being generated, and wrap-ups not being generated.
-
monitoring Mar 12, 2026, 03:17 AM UTC
The platform provider has implemented mitigation steps and error rates have resolved. Monitoring for stability before resolving.
-
resolved Mar 12, 2026, 03:26 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 01:18 PM UTC
- Resolved
- Mar 01, 2026, 01:39 PM UTC
- Duration
- 20m
Affected: EMEA (UAE)
Timeline · 2 updates
-
investigating Mar 01, 2026, 01:18 PM UTC
Teams are investigating an issue impacting multiple features in the Genesys Cloud platform. The platform provider has been engaged and is actively assisting in the incident. Next update 09:15 Eastern or sooner as information becomes available.
-
resolved Mar 01, 2026, 01:39 PM UTC
Genesys is continuing to monitor activities in the region with the platform provider. Genesys Cloud services are operating normally after evacuating services from a single availability zone. There is no current impact to our customers. We will provide immediate updates through this channel should there be any change in status.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 08:49 AM UTC
- Resolved
- Feb 26, 2026, 09:36 AM UTC
- Duration
- 47m
Affected: EMEA (Dublin)
Timeline · 4 updates
-
investigating Feb 26, 2026, 08:49 AM UTC
Teams are investigating an issue impacting voice bot flows and third party bot flows. Digital bot flows will remain unaffected. Next update 04:30 Eastern or sooner as information becomes avaialble.
-
monitoring Feb 26, 2026, 09:30 AM UTC
Service teams identified the root cause as an issue with the speech-to-text provider and have worked with the vendor to restore service. Error rates have returned to normal and we continue to monitor for stability.
-
monitoring Feb 26, 2026, 09:31 AM UTC
We are continuing to monitor for any further issues.
-
resolved Feb 26, 2026, 09:36 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 11:18 AM UTC
- Resolved
- Feb 02, 2026, 01:07 PM UTC
- Duration
- 1h 48m
Affected: Asia Pacific (Tokyo)
Timeline · 4 updates
-
investigating Feb 02, 2026, 11:18 AM UTC
Teams are investigating an issue causing latency with real-time conversation and user detail records in the Tokyo region. Next update 07:00 Eastern or sooner as information becomes available.
-
investigating Feb 02, 2026, 12:01 PM UTC
mitigation steps have been implemented. Customers may continue to experience delays until the backlogged events are successfully processed. Next update 07:45 Eastern or sooner as information becomes available.
-
investigating Feb 02, 2026, 12:35 PM UTC
The service team has implemented additional mitigation actions and we are actively monitoring their effectiveness. We continue to process the backlog of events while working to restore full service performance. Next update 08:30 or sooner as information becomes available.
-
resolved Feb 02, 2026, 01:07 PM UTC
The backlogged events have been successfully processed and the service is operating as expected
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 01:48 PM UTC
- Resolved
- Jan 29, 2026, 06:03 PM UTC
- Duration
- 4h 14m
Affected: Americas (Sao Paulo)Asia Pacific (Mumbai)
Timeline · 6 updates
-
investigating Jan 29, 2026, 01:48 PM UTC
We are currently investigating an issue that has resulted in missing data in the Analytics dashboards. Our team is working to identify the root cause and restore the missing data as soon as possible. Next update 09:45 Eastern or sooner as information becomes available.
-
identified Jan 29, 2026, 02:38 PM UTC
The root cause has been identified, and a plan has been developed to restore the missing data to the Analytics dashboards. The restoration process is currently being tested in the development environment before executing in the production environment. Next update 10:45 Eastern or sooner as information becomes available.
-
identified Jan 29, 2026, 03:43 PM UTC
Teams are continuing to test the data restoration process in the development environment. Once the testing phase has been completed successfully and we are confident in the process, we will move forward with execution in production to restore data in the Analytics dashboards. Next update 11:45 Eastern or sooner as information becomes available.
-
identified Jan 29, 2026, 04:44 PM UTC
Teams are beginning the recovery process in production, beginning with the Sao Paulo region. Next update 12:45 Eastern or sooner as information becomes available.
-
identified Jan 29, 2026, 05:36 PM UTC
Restoration is completed in Mumbai. Restoration is continuing in Sao Paulo. We are able to confirm data restored as mitigation steps are implemented. Next update 13:45 or sooner as information becomes available.
-
resolved Jan 29, 2026, 06:03 PM UTC
All data has been restored. Incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 12:38 PM UTC
- Resolved
- Jan 29, 2026, 12:38 PM UTC
- Duration
- —
Affected: Americas (Sao Paulo)Asia Pacific (Mumbai)
Timeline · 1 update
-
resolved Jan 29, 2026, 12:38 PM UTC
Between 4:30 AM and 7:07 AM Eastern Time, customers in the Sao Paulo and Mumbai regions experienced issues with Analytics dashboards not loading correctly. Our service team has successfully resolved the incident, and all Analytics dashboards are now functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 06:45 PM UTC
- Resolved
- Jan 23, 2026, 07:04 PM UTC
- Duration
- 19m
Affected: Americas (US East)
Timeline · 3 updates
-
identified Jan 23, 2026, 06:45 PM UTC
Teams are investigating error reports when setting agent status, causing some agents to not receive ACD calls. Some users have experienced improvement after refreshing the browser and/or logging out and back in. Fix actions are being applied. Next update top of the hour.
-
monitoring Jan 23, 2026, 06:53 PM UTC
Fix actions have resulted reduction of errors. Affected agents should refresh their status. Monitoring for stability.
-
resolved Jan 23, 2026, 07:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 11, 2026, 10:36 AM UTC
- Resolved
- Jan 11, 2026, 11:21 AM UTC
- Duration
- 45m
Affected: Americas (Sao Paulo)Americas (US East)Americas (Canada)Asia Pacific (Mumbai)Asia Pacific (Sydney)Asia Pacific (Seoul)EMEA (Dublin)EMEA (Frankfurt)EMEA (London)EMEA (Zurich)EMEA (UAE)Americas (Mexico)Asia Pacific (Singapore)
Timeline · 3 updates
-
identified Jan 11, 2026, 10:36 AM UTC
Some customers may experience issues creating or modifying new call routing configurations. Existing call flows and configurations continue to work normally. Our engineering team has identified the issue and mitigation steps are being implemented. Next update top of the hour.
-
identified Jan 11, 2026, 11:03 AM UTC
Root cause of the issue has been identified and the team continues to take steps to mitigate. Next update in 1 hour or sooner as information becomes available.
-
resolved Jan 11, 2026, 11:21 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 07:58 AM UTC
- Resolved
- Jan 09, 2026, 07:58 AM UTC
- Duration
- —
Affected: Asia Pacific (Tokyo)
Timeline · 1 update
-
resolved Jan 09, 2026, 07:58 AM UTC
Genesys Cloud service teams identified an issue impacting WebRTC calls. Mitigation steps have been implemented and error rates have improved. Customers needing a formal RCA should open a case where it will be attached. Impact period was 06:37GMT-07:46GMT.
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2025, 04:08 PM UTC
- Resolved
- Dec 23, 2025, 04:08 PM UTC
- Duration
- —
Affected: Americas (US East)
Timeline · 1 update
-
resolved Dec 23, 2025, 04:08 PM UTC
Between 10:10 AM ET and 10:45 AM ET, some customers experienced issues with new inbound and outbound calls. During this 35-minute period, while existing calls remained connected, new calls were unable to complete successfully. Customers may have also experienced issues with call control functions such as transfers and holds. Our engineering team identified and resolved the issue, and service was fully restored by 10:45 AM ET.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 02:18 PM UTC
- Resolved
- Dec 16, 2025, 02:47 PM UTC
- Duration
- 29m
Affected: EMEA (Dublin)EMEA (Frankfurt)EMEA (London)
Timeline · 4 updates
-
investigating Dec 16, 2025, 02:18 PM UTC
Teams are investigating an issue where agents are unable to end callbacks due to call controls being grayed out. Next update 09:45 Eastern or sooner as information becomes available.
-
identified Dec 16, 2025, 02:38 PM UTC
Root cause of the issue has been identified and the team is taking steps to mitigate. Next update 10:15 Eastern or sooner as information becomes available.
-
monitoring Dec 16, 2025, 02:44 PM UTC
Mitigation steps have been implemented. Customers will need to refresh the Genesys Cloud client for changes to take effect.
-
resolved Dec 16, 2025, 02:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 29, 2025, 04:11 PM UTC
- Resolved
- Nov 28, 2025, 06:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 29, 2025, 04:11 PM UTC
On November 28, 2025, between 06:30 and 07:25 GMT, some customers in the APAC (Tokyo) region experienced issues with voice services. During this time, users may have encountered intermittent failures with inbound and outbound calls, difficulties with call controls, and error messages related to station status. The issue auto resolved and services are operating normally. Our service teams are conducting a thorough investigation of the incident and a detailed root cause analysis will be provided once the investigation is complete.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 11:29 PM UTC
- Resolved
- Nov 13, 2025, 01:57 AM UTC
- Duration
- 2h 27m
Affected: EMEA (Frankfurt)
Timeline · 5 updates
-
identified Nov 12, 2025, 11:29 PM UTC
Genesys Cloud has identified an issue impacting real-time analytics. Users may experience temporary delays for analytics and reporting functions. Mitigation steps are being implemented at this time. Next update top of the hour.
-
identified Nov 13, 2025, 12:32 AM UTC
While initial mitigation steps have been implemented, they have not resolved the underlying issue. Our engineering teams are actively investigating the root cause and working toward a resolution. Customers will continue to experience delays with analytics and reporting functions until this issue is resolved and the backlogged events are processed. Next update 20:30 Eastern or sooner as information becomes available.
-
identified Nov 13, 2025, 01:34 AM UTC
Our engineering teams continue investigating the root cause and are working toward a resolution. Next update 21:30 Eastern or sooner as information becomes available.
-
identified Nov 13, 2025, 01:42 AM UTC
Our development teams have implemented multiple remediation strategies and we are beginning to see improvement. Customers will continue to see delays in analytics data until the backlogged events are processed. Next updated 21:45 Eastern or sooner as information becomes available.
-
resolved Nov 13, 2025, 01:57 AM UTC
The backlogged events have been processed and service is fully recovered
Read the full incident report →
- Detected by Pingoru
- Oct 27, 2025, 06:04 PM UTC
- Resolved
- Oct 27, 2025, 07:01 PM UTC
- Duration
- 57m
Affected: Americas (US West)
Timeline · 3 updates
-
identified Oct 27, 2025, 06:04 PM UTC
Genesys Cloud has identified an issue impacting real time analytics. Mitigation steps have been implemented and the service is in recovery. Interaction data will be delayed until the backlogged events have been processed. Next update 14:45 Eastern.
-
identified Oct 27, 2025, 06:45 PM UTC
The service is continuing to process backlogged events. Additional mitigation steps have been implemented to help speed recovery. Next update 15:30 Eastern.
-
resolved Oct 27, 2025, 07:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 09:14 PM UTC
- Resolved
- Oct 23, 2025, 09:34 PM UTC
- Duration
- 20m
Affected: Americas (Sao Paulo)Americas (US East)
Timeline · 3 updates
-
monitoring Oct 23, 2025, 09:14 PM UTC
Between 16:38 and 16:54, Genesys customers in the US East, São Paulo and Tokyo regions experienced connectivity issues with Genesys Cloud. Users were able to reconnect after multiple attempts using retry logic. The issue has been resolved and services are now operating normally.
-
monitoring Oct 23, 2025, 09:19 PM UTC
We are continuing to monitor for any further issues.
-
resolved Oct 23, 2025, 09:34 PM UTC
This incident has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 11:17 AM UTC
- Resolved
- Oct 20, 2025, 10:54 PM UTC
- Duration
- 11h 36m
Affected: Americas (US East)
Timeline · 28 updates
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 07:33 AM UTC
- Resolved
- Oct 16, 2025, 08:00 AM UTC
- Duration
- 26m
Affected: Americas (Sao Paulo)
Timeline · 3 updates
-
investigating Oct 16, 2025, 07:33 AM UTC
Development teams are investigating an issue impacting real time analytics in Sao Paulo region. Customers may experience delays with user presence, aggregate metrics, observation metrics, and notifications. Mitigation steps have been implemented, and we are monitoring for improvement.
-
monitoring Oct 16, 2025, 07:49 AM UTC
Mitigation steps were successful, with error rates continuing to decline. Next update: 04:00 AM ET, or earlier if new information becomes available.
-
resolved Oct 16, 2025, 08:00 AM UTC
Error rates have returned to normal, and the backlogged events have been successfully processed. Issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 11:30 AM UTC
- Resolved
- Oct 15, 2025, 10:19 PM UTC
- Duration
- 10h 49m
Affected: Americas (Sao Paulo)Americas (Canada)Asia Pacific (Seoul)FedRAMPEMEA (UAE)Asia Pacific (Osaka)
Timeline · 10 updates
Read the full incident report →