- Detected by Pingoru
- Sep 26, 2025, 07:06 PM UTC
- Resolved
- Sep 26, 2025, 08:36 PM UTC
- Duration
- 1h 30m
Affected: Americas (US West)
Timeline · 5 updates
-
identified Sep 26, 2025, 07:06 PM UTC
Teams are investigating latent conditions with assignment functions at this time. Next update bottom of the hour.
-
identified Sep 26, 2025, 07:27 PM UTC
Error counts are decreasing; additional mitigation steps are in progress to speed recovery. Next update top of the hour.
-
identified Sep 26, 2025, 08:01 PM UTC
Additional mitigation steps completed; recovery in progress as backlog processing completes. Next update bottom of the hour.
-
monitoring Sep 26, 2025, 08:11 PM UTC
Backlog has cleared; monitoring for stability.
-
resolved Sep 26, 2025, 08:36 PM UTC
Genesys Cloud customers experienced service delays affecting conversation routing in the US West region. During the incident, users may have experienced extended queue times and delayed agent assignments. The development team identified root cause as a database performance issue. After initial mitigation steps were taken, improvement was observed. Final mitigation steps were implemented at 4:02 PM. Queue times returned to expected levels once backlogged events completed processing.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2025, 10:42 PM UTC
- Resolved
- Jul 30, 2025, 11:05 PM UTC
- Duration
- 23m
Affected: Americas (US West)
Timeline · 3 updates
-
identified Jul 30, 2025, 10:42 PM UTC
Teams are investigating an issue that is intermittently impacting users ability to make and receive WebRTC calls. Mitigation steps have been implemented and we are seeing improvement. Next update 19:00 Eastern.
-
monitoring Jul 30, 2025, 10:52 PM UTC
Error rates have subsided and all health checks are passing successfully. Monitoring for stability before resolving.
-
resolved Jul 30, 2025, 11:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 02:22 PM UTC
- Resolved
- Jul 23, 2025, 02:59 PM UTC
- Duration
- 36m
Affected: EMEA (Dublin)EMEA (Frankfurt)
Timeline · 3 updates
-
monitoring Jul 23, 2025, 02:22 PM UTC
Genesys Cloud service teams have identified an issue intermittently impacting WebRTC calls. Mitigation steps have been implemented and error rates have improved. Next update 10:45 AM Eastern.
-
monitoring Jul 23, 2025, 02:42 PM UTC
Error rates have returned to normal. We continue to monitor for stability as issue was intermittent. Next update 11:00 Eastern
-
resolved Jul 23, 2025, 02:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2025, 03:13 PM UTC
- Resolved
- Jul 08, 2025, 04:15 PM UTC
- Duration
- 1h 2m
Affected: EMEA (Zurich)
Timeline · 3 updates
-
identified Jul 08, 2025, 03:13 PM UTC
Some customers in the Zurich region may experience issues updating and creating work items. This is a continuation of the previous incident in which the platform provider is performing additional work to restore service to certain lambda functions. Next update 12:00 Eastern or sooner as information becomes available.
-
identified Jul 08, 2025, 04:02 PM UTC
The platform provider continues to work toward resolution. Some services are seeing improvement but users may still experience issues with work items. Next update 12:45 Eastern or sooner as information becomes available.
-
resolved Jul 08, 2025, 04:15 PM UTC
The platform provider has resolved this issue.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2025, 11:18 AM UTC
- Resolved
- Jul 08, 2025, 12:10 PM UTC
- Duration
- 51m
Affected: EMEA (Frankfurt)
Timeline · 6 updates
-
investigating Jul 08, 2025, 11:18 AM UTC
Users may experience temporary delays for analytics and reporting functions. Mitigation steps are being implemented at this time. Next update top of the hour.
-
investigating Jul 08, 2025, 11:24 AM UTC
Mitigation steps have been applied. Recovery is in progress.
-
investigating Jul 08, 2025, 11:33 AM UTC
Errors returned, additional mitigation steps are being applied. Next update top of the hour.
-
investigating Jul 08, 2025, 11:43 AM UTC
Latest mitigation steps have proven successful. Monitoring recovery. Next update top of the hour.
-
monitoring Jul 08, 2025, 11:59 AM UTC
Teams will continue to monitor to ensure stability. Health checks are normal.
-
resolved Jul 08, 2025, 12:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2025, 01:52 PM UTC
- Resolved
- Jul 07, 2025, 02:24 PM UTC
- Duration
- 31m
Affected: EMEA (Frankfurt)
Timeline · 4 updates
-
investigating Jul 07, 2025, 01:52 PM UTC
Agents that were impacted from the interaction assignment incident from this morning should cycle their presence to reset their status.
-
identified Jul 07, 2025, 02:09 PM UTC
The original symptoms from the earlier incident have recurred. The development team has applied additional mitigation steps. Monitoring results at this time. Next update bottom of the hour.
-
monitoring Jul 07, 2025, 02:15 PM UTC
Health checks are improving. Monitoring for stability. Orgs that continue to experience stuck interactions please work with product support if unable to clear. https://help.mypurecloud.com/articles/disconnect-interactions/
-
resolved Jul 07, 2025, 02:24 PM UTC
This incident has been resolved. Teams will continue review and attach RCA to reported cases when finalized.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2025, 07:53 AM UTC
- Resolved
- Jul 07, 2025, 09:13 AM UTC
- Duration
- 1h 20m
Affected: EMEA (Frankfurt)EMEA (Frankfurt)
Timeline · 6 updates
-
investigating Jul 07, 2025, 07:53 AM UTC
Genesys Cloud has identified an issue impacting inbound call routing. Teams are working to triage and determine next steps.
-
investigating Jul 07, 2025, 07:54 AM UTC
We are continuing to investigate this issue.
-
investigating Jul 07, 2025, 08:47 AM UTC
Mitigation steps have been applied. Pending health check review. Next update top of the hour.
-
investigating Jul 07, 2025, 09:03 AM UTC
Monitoring for stability. The service is in recovery. Impacted orgs should refresh presence status for agents.
-
investigating Jul 07, 2025, 09:12 AM UTC
The issue has been resolved. Any orgs who experience stuck interactions should refer to https://help.mypurecloud.com/articles/disconnect-interactions/ for assistance. If additional assistance is needed to help clear interactions, please contact product support.
-
resolved Jul 07, 2025, 09:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2025, 08:50 PM UTC
- Resolved
- Jul 03, 2025, 11:29 PM UTC
- Duration
- 2h 39m
Affected: Americas (US East)Americas (US West)
Timeline · 6 updates
-
identified Jul 03, 2025, 08:50 PM UTC
Some customers may be experiencing elevated error rates for Lex v2 flows. The Genesys team is working with the platform provider at this time. Next update 5:30pm ET or as information becomes available.
-
identified Jul 03, 2025, 09:18 PM UTC
Teams are continuing troubleshooting efforts with the platform provider to determine root cause and next steps. Next update 6:15pm ET or as information becomes available.
-
identified Jul 03, 2025, 10:18 PM UTC
The platform provider is continuing to troubleshoot the issue for root cause and mitigation. Next update 1 hour or as information becomes available.
-
identified Jul 03, 2025, 11:13 PM UTC
Error rates are decreasing. Pending update from the platform provider. Next update 8:15pm ET or as information becomes available.
-
monitoring Jul 03, 2025, 11:28 PM UTC
Platform provider advised services should be in recovery. Health checks have returned to normal. Monitoring for stability.
-
resolved Jul 03, 2025, 11:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 24, 2025, 05:14 PM UTC
- Resolved
- Jun 24, 2025, 05:35 PM UTC
- Duration
- 20m
Affected: Americas (US West)
Timeline · 3 updates
-
investigating Jun 24, 2025, 05:14 PM UTC
Development teams are investigating an issue impacting Analytics Detail Records. Next update 13:45 Eastern or sooner as information becomes available.
-
identified Jun 24, 2025, 05:25 PM UTC
Mitigation steps have been implemented and we are seeing improvement. Next update 14:00 or sooner as information becomes available.
-
resolved Jun 24, 2025, 05:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 03:16 PM UTC
- Resolved
- Jun 18, 2025, 03:52 PM UTC
- Duration
- 36m
Affected: Americas (Sao Paulo)Americas (US East)
Timeline · 4 updates
-
identified Jun 18, 2025, 03:16 PM UTC
Genesys Cloud customers using the WhatsApp integration may be experiencing errors with messages that contain emojis. The development team has implemented mitigation steps. Next update bottom of the hour.
-
monitoring Jun 18, 2025, 03:41 PM UTC
Recovery is in progress after mitigation steps.
-
monitoring Jun 18, 2025, 03:48 PM UTC
Monitoring for stability
-
resolved Jun 18, 2025, 03:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:44 PM UTC
- Resolved
- Jun 12, 2025, 11:36 PM UTC
- Duration
- 4h 51m
Affected: Americas (Sao Paulo)Americas (US East)Americas (US West)Americas (Canada)FedRAMPAsia Pacific (Mumbai)Asia Pacific (Sydney)Asia Pacific (Tokyo)Asia Pacific (Seoul)EMEA (Dublin)EMEA (Frankfurt)EMEA (London)EMEA (Zurich)EMEA (UAE)Asia Pacific (Osaka)
Timeline · 7 updates
-
identified Jun 12, 2025, 06:44 PM UTC
Customers may be experiencing errors using TTS, STT, and bot flows. A case has been opened with the vendor. For speech-to-text issues, users should select Genesys Enhanced v2 as the speech-to-text provider in the bot flow. For text-to-speech (TTS), users need to select a non-Google voice. Bot flows will take the configured default path.
-
identified Jun 12, 2025, 07:19 PM UTC
The vendor has advised mitigation steps are in progress with some recovery observed. No ETR at this time.
-
monitoring Jun 12, 2025, 07:43 PM UTC
The vendor advised they have largely recovered. Genesys will monitor until the all clear is received.
-
monitoring Jun 12, 2025, 08:02 PM UTC
Genesys is still seeing errors from the vendor but does note improvement since incident started. Pending final resolution from the vendor.
-
monitoring Jun 12, 2025, 08:23 PM UTC
TTS and STT are healthy at this time. Errors are still being observed on Dialogflow. Pending status from vendor.
-
monitoring Jun 12, 2025, 09:08 PM UTC
Dialogflow errors have ceased. The vendor is reporting recovery but has not provided the all clear. Will continue to monitor.
-
resolved Jun 12, 2025, 11:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 14, 2025, 09:39 PM UTC
- Resolved
- May 14, 2025, 09:45 PM UTC
- Duration
- 6m
Affected: Americas (Sao Paulo)
Timeline · 2 updates
-
identified May 14, 2025, 09:39 PM UTC
Customers may be experiencing delays with real time analytics and reporting. Mitigation steps have been implemented. Next update 30 min or as information becomes available.
-
resolved May 14, 2025, 09:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2025, 11:16 AM UTC
- Resolved
- May 05, 2025, 11:45 AM UTC
- Duration
- 28m
Affected: EMEA (Dublin)
Timeline · 3 updates
-
investigating May 05, 2025, 11:16 AM UTC
Customers are experiencing issues with voice bot flows causing some calls to fail. Mitigation steps are being implemented. Next update 07:30 Eastern
-
monitoring May 05, 2025, 11:23 AM UTC
Error rates have returned to normal levels and customers are seeing improvement.
-
resolved May 05, 2025, 11:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 02, 2025, 07:45 PM UTC
- Resolved
- May 02, 2025, 07:52 PM UTC
- Duration
- 7m
Affected: Asia Pacific (Mumbai)
Timeline · 2 updates
-
monitoring May 02, 2025, 07:45 PM UTC
Elevated error rates have been identified in the APAC (Mumbai) region. Services are now in recovery. Monitoring for stability.
-
resolved May 02, 2025, 07:52 PM UTC
This incident has been resolved. Customers that experience any stuck interactions should follow instructions provided https://help.mypurecloud.com/articles/disconnect-interactions/. If unable to resolve, please open a case with Product Support for assistance.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2025, 06:11 PM UTC
- Resolved
- Apr 25, 2025, 08:11 PM UTC
- Duration
- 2h
Affected: Americas (Sao Paulo)Americas (US East)Americas (US West)Americas (Canada)FedRAMPAsia Pacific (Mumbai)Asia Pacific (Sydney)Asia Pacific (Tokyo)Asia Pacific (Seoul)EMEA (Dublin)EMEA (Frankfurt)EMEA (London)EMEA (Zurich)EMEA (UAE)Asia Pacific (Osaka)
Timeline · 8 updates
-
investigating Apr 25, 2025, 06:11 PM UTC
We are investigating an issue with degraded performance in both the web and desktop applications. Next update 14:30 or sooner as information becomes available.
-
investigating Apr 25, 2025, 06:31 PM UTC
A mitigation plan has been implemented and is currently undergoing testing to verify its effectiveness in resolving the performance issues. Next update 14:45 PM Eastern or sooner as information becomes available.
-
investigating Apr 25, 2025, 06:54 PM UTC
Despite initial mitigation attempts showing minimal improvement, symptoms temporarily resolve upon client refresh but return with continued use. Multiple service teams are now collaborating to identify and address the root cause. Next update 15:15 PM or sooner as information becomes available.
-
investigating Apr 25, 2025, 07:14 PM UTC
Investigation remains ongoing across multiple teams. While testing continues, no new mitigation steps have been identified at this time. Next update 15:45 Eastern or sooner as information becomes available
-
investigating Apr 25, 2025, 07:31 PM UTC
We are continuing to investigate this issue.
-
investigating Apr 25, 2025, 07:33 PM UTC
Additional mitigation steps have been implemented and testing is in progress. Customers who would like to test should refresh any open clients and attempt to use the application again.
-
monitoring Apr 25, 2025, 08:07 PM UTC
System operations have returned to normal levels. Continuous monitoring remains in place to ensure stability.
-
resolved Apr 25, 2025, 08:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2025, 11:40 AM UTC
- Resolved
- Apr 25, 2025, 01:20 PM UTC
- Duration
- 1h 40m
Affected: Americas (US East)Americas (US West)Americas (Canada)Asia Pacific (Sydney)Asia Pacific (Tokyo)EMEA (Dublin)EMEA (Frankfurt)EMEA (London)
Timeline · 6 updates
-
investigating Apr 25, 2025, 11:40 AM UTC
We are investigating an issue that is impacting customers ability to answer interactions due to latency in the UI.
-
investigating Apr 25, 2025, 12:02 PM UTC
Teams are continuing to investigate root cause for latency in the UI. Next update 08:30 AM Eastern
-
investigating Apr 25, 2025, 12:36 PM UTC
Service teams are continuing to actively investigate this issue. Next update 09:00 AM Eastern or sooner if information becomes available.
-
identified Apr 25, 2025, 12:58 PM UTC
Root cause has been identified and mitigation steps have been put in place. Customers should begin to see recovery.
-
monitoring Apr 25, 2025, 01:05 PM UTC
Page rendering errors have subsided. Customers who are already logged in should reload their browser or refresh the desktop application to access the updated version. Agents logging in for the first time will be promptly notified of a new client version and should update accordingly.
-
resolved Apr 25, 2025, 01:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 08:48 AM UTC
- Resolved
- Apr 15, 2025, 08:58 AM UTC
- Duration
- 10m
Affected: Asia Pacific (Tokyo)
Timeline · 2 updates
-
investigating Apr 15, 2025, 08:48 AM UTC
Customers in the APAC (Toyko) region may be experiencing delays with analytics and reporting. Teams are investigating at this time to determine next steps. Next update top of the hour or as information becomes available.
-
resolved Apr 15, 2025, 08:58 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2025, 05:30 PM UTC
- Resolved
- Mar 27, 2025, 05:55 PM UTC
- Duration
- 24m
Affected: Americas (US West)
Timeline · 3 updates
-
identified Mar 27, 2025, 05:30 PM UTC
Elevated error rates have been identified in the Americas (US West) region. Customers may be experiencing issues with call notifications, answering calls, and completing calls. Teams are engaged for triage and mitigation. Next update 15 minutes.
-
identified Mar 27, 2025, 05:38 PM UTC
Mitigation steps are in progress; next update top of the hour.
-
resolved Mar 27, 2025, 05:55 PM UTC
Health checks are normal. Resolving incident. All clear time 1:45pm ET.
Read the full incident report →