VMware Workspace ONE Outage History

Started Apr 22, 2026, 03:35 PM UTC· resolved Apr 23, 2026, 05:39 AM UTC

1. scheduled Apr 22, 2026, 03:35 PM UTC

   Horizon Cloud Service First-Gen is undergoing the weekly scheduled maintenance on the Horizon Cloud Console Access. Maintenance Window: • Start: Wednesday, April 29, 2026, 03:30 UTC • End: Wednesday, April 29, 2026, 06:30 UTC Impact: • There is no impact on end-users and their ability to connect to their desktops. • During this maintenance there will be a brief (not more than 2 minutes) downtime on the Administration Console. Administrative functions will be unavailable or may appear offline during this period. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems. Additional Information and Support: Please visit Service Support Website at Customer Connect (https://customerconnect.omnissa.com/home) to submit a case through Customer Connect. For information on contacting service support, see How to file a Support Request in Customer Connect (https://kb.omnissa.com/s/article/2006985). Thanks for your patience. Additional Information: Omnissa Horizon Cloud Service Team will provide additional updates on our Unified Status page (http://status.workspaceone.com) until the maintenance activity is complete.

Read the full incident report →

Started Apr 22, 2026, 02:43 PM UTC· resolved Apr 22, 2026, 05:55 PM UTC

1. identified Apr 22, 2026, 02:43 PM UTC

   Omnissa Workspace ONE is investigating reports of performance issues with SaaS environments. Operations teams have identified the issue is impacting data loading on these pages: -Device list -Application list -Event log -Deployment tracking The issue has been identified and a resolution is actively being implemented. Omnissa Cloud Services portal has been updated for customers affected by this event. Please check the Omnissa Cloud Services portal to confirm if your environment is affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. identified Apr 22, 2026, 03:31 PM UTC

   Omnissa Workspace ONE has noted partial recovery with some missing data being made available on the affected pages. Omnissa teams will continue working to have all data made available. Operations teams continue to actively work towards complete recovery.

3. identified Apr 22, 2026, 04:16 PM UTC

   Omnissa Workspace ONE has noted partial recovery with SaaS environments and continues to work towards complete rcovery. Operations teams continue to actively work towards complete recovery.

4. identified Apr 22, 2026, 05:39 PM UTC

   Omnissa Workspace ONE has noted all underlying issues have been resolved and missing data is continuing to be made available. Operations teams continue to actively work towards complete recovery.

5. resolved Apr 22, 2026, 05:55 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Operations teams will continue to monitor system performance levels and investigate the root cause of the issue. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Apr 22, 2026, 09:59 AM UTC· resolved Apr 22, 2026, 12:31 PM UTC

1. identified Apr 22, 2026, 09:59 AM UTC

   The Horizon Cloud team is currently investigating an issue impacting VM provisioning rates in the Japan region. Customers may experience delays or failures when creating, deleting, or updating Desktop Pools. We are actively working to determine the root cause and will provide updates as more information becomes available.

2. identified Apr 22, 2026, 10:57 AM UTC

   Customers may experience delays or failures when creating, deleting, or updating Desktop Pools in the Japan Region. We are actively working to mitigate the issue and will provide updates as more information becomes available.

3. monitoring Apr 22, 2026, 12:02 PM UTC

   Horizon Cloud Service Next-Gen has completed actions to remediate the issues and confirm that the services are available. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

4. resolved Apr 22, 2026, 12:31 PM UTC

   The issue is resolved. If you are experiencing any residual effects from this issue, please open a Service Request for assistance. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Apr 21, 2026, 05:38 PM UTC· resolved Apr 28, 2026, 02:34 PM UTC

1. scheduled Apr 21, 2026, 05:38 PM UTC

   Omnissa Connect are performing maintenance on infrastructure in United States. Services will remain accessible during the update with only a few minutes of possibly slower response times and, in some cases, a small number of failed request that are expected to succeed on retry. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. scheduled Apr 28, 2026, 10:30 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress Apr 28, 2026, 11:30 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:43 AM UTC· resolved May 16, 2026, 07:25 PM UTC

1. scheduled Apr 19, 2026, 11:43 AM UTC

   Workspace ONE UEM is scheduled to undergo maintenance on May 16th, 2026. Maintenance Window: • Start: Saturday, May 16th, 2026, 15:00 UTC • End: Saturday, May 16th, 2026, 19:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users may experience intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 16, 2026, 02:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 16, 2026, 03:00 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:40 AM UTC· resolved May 10, 2026, 05:01 AM UTC

1. scheduled Apr 19, 2026, 11:40 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 10th, 2026 Maintenance Window: • Start: Sunday, May 10th, 2026, 1:00 UTC • End: Sunday, May 10th, 2026, 5:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users can expect intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 10, 2026, 12:00 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 10, 2026, 01:00 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:36 AM UTC· resolved May 09, 2026, 04:58 AM UTC

1. scheduled Apr 19, 2026, 11:36 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 9th, 2026. Maintenance Window: • Start: Saturday, May 9th, 2026, 1:00 UTC • End: Saturday, May 9th, 2026, 5:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users can expect intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 09, 2026, 12:00 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 09, 2026, 01:00 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:34 AM UTC· resolved May 09, 2026, 05:16 AM UTC

1. scheduled Apr 19, 2026, 11:34 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 9th, 2026. Maintenance Window: • Start: Saturday, May 9th, 2026, 1:00 UTC • End: Saturday, May 9th, 2026, 5:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users can expect intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 09, 2026, 12:00 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 09, 2026, 01:00 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

4. in progress May 09, 2026, 05:04 AM UTC

   Scheduled maintenance is taking longer than expected and is running over the allotted window. Please standby for further updates. During this delay, service will be available for end-users who may experience intermittent latency and timeouts. We appreciate your patience and continued support while we continue to improve our systems. System reliability is a top priority at Omnissa Workspace ONE.

Read the full incident report →

Started Apr 19, 2026, 11:32 AM UTC· resolved May 09, 2026, 04:58 AM UTC

1. scheduled Apr 19, 2026, 11:32 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 9th, 2026. Maintenance Window: • Start: Saturday, May 9th, 2026, 1:00 UTC • End: Saturday, May 9th, 2026, 5:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users can expect intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 09, 2026, 12:00 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 09, 2026, 01:00 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:28 AM UTC· resolved May 08, 2026, 07:22 PM UTC

1. scheduled Apr 19, 2026, 11:28 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 8th, 2026 Maintenance Window: • Start: Friday, May 8th, 2026, 15:00 UTC • End: Friday, May 8th, 2026, 19:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users may experience intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 08, 2026, 02:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 08, 2026, 03:01 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:25 AM UTC· resolved May 08, 2026, 07:22 PM UTC

1. scheduled Apr 19, 2026, 11:25 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 8th, 2026 Maintenance Window: • Start: Friday, May 8th, 2026, 15:00 UTC • End: Friday, May 8th, 2026, 19:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users may experience intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 08, 2026, 02:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 08, 2026, 03:00 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 11:20 AM UTC· resolved May 08, 2026, 07:22 PM UTC

1. scheduled Apr 19, 2026, 11:20 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 8th, 2026 Maintenance Window: • Start: Friday, May 8th, 2026, 15:00 UTC • End: Friday, May 8th, 2026, 19:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users may experience intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 08, 2026, 02:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 08, 2026, 03:00 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 19, 2026, 09:59 AM UTC· resolved May 08, 2026, 07:22 PM UTC

1. scheduled Apr 19, 2026, 09:59 AM UTC

   Workspace ONE UEM and Assist are scheduled to undergo maintenance on May 8th, 2026 Maintenance Window: • Start: Friday, May 8th, 2026, 15:00 UTC • End: Friday, May 8th, 2026, 19:00 UTC Change: Infrastructure Patching Customer Impact: Omnissa Cloud Services portal has been updated for all customers in scope for this maintenance. During the window customer end-users may experience intermediate latency and timeouts. Downtime: 5 min on average System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 08, 2026, 02:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 08, 2026, 03:01 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 17, 2026, 10:49 PM UTC· resolved Apr 20, 2026, 02:39 AM UTC

1. investigating Apr 17, 2026, 10:49 PM UTC

   Omnissa Workspace ONE is investigating reports of availability issues with SaaS environments. Omnissa Cloud Services portal has been updated for customers affected by this event. Integrations calling UEM API using OAuth token may fail. This may include: -Automations or custom scripts using WS1 UEM APIs using OAuth -Third-party integrations (e.g., ServiceNow) using OAuth Please check the Omnissa Cloud Services portal to confirm if your environment is affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. investigating Apr 17, 2026, 11:31 PM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams are actively working to resolve it.

3. identified Apr 18, 2026, 12:36 AM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams have identified an issue with DNS for *.uemauth.vmwservices.com domains which is continuing to propagate globally. While we continue to work on resolving this issue with these domains, there are other *.uemauth.workspaceone.com domains for the same resources that are currently available. If you are are currently experiencing issues you can update to *.uemauth.workspaceone.com. There is already an active plan to migrate to the new domains detailed in this KB: https://kb.omnissa.com/s/article/6001352. The process described there can be used to update the domains to resolve these issues.

4. identified Apr 18, 2026, 02:02 AM UTC

   A correction has been made to top-level DNS for vmwservices.com and is propagating now. Customers may still follow the instructions in the KB article for faster remediation.

5. monitoring Apr 18, 2026, 03:11 AM UTC

   Omnissa Workspace ONE has noted partial recovery. A correction has been made to top-level DNS for vmwservices.com and is propagating now. Omnissa expects the correction to completely propagate over the next 24-48 hours. For customers seeing immediate impact and needing a more timely resolution - Omnissa recommends they consider following the instructions in the KB article (https://kb.omnissa.com/s/article/6001352) to cutover to *.uemauth.workspaceone.com. Omnissa Workspace ONE continues to actively monitor the situation towards complete recovery and will update the status page on complete recovery. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

6. monitoring Apr 18, 2026, 03:29 PM UTC

   Omnissa Workspace ONE continues to see recovery. DNS propagation is continuing and Omnissa expects the correction to completely propagate within the next 36 hours. For customers seeing immediate impact and needing a more timely resolution - Omnissa recommends they consider following the instructions in the KB article (https://kb.omnissa.com/s/article/6001352) to cutover to *.uemauth.workspaceone.com. Omnissa Workspace ONE continues to actively monitor the situation towards complete recovery and will update the status page on complete recovery. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

7. monitoring Apr 19, 2026, 05:37 AM UTC

   Omnissa Workspace ONE continues to see recovery. DNS propagation is continuing and Omnissa expects the correction to completely propagate within the next 22 hours. For customers seeing immediate impact and needing a more timely resolution - Omnissa recommends they consider following the instructions in the KB article (https://kb.omnissa.com/s/article/6001352) to cutover to *.uemauth.workspaceone.com. Omnissa Workspace ONE continues to actively monitor the situation towards complete recovery and will update the status page on complete recovery. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

8. resolved Apr 20, 2026, 02:39 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Operations teams will continue to monitor system performance levels and investigate the root cause of the issue. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Apr 17, 2026, 09:49 PM UTC· resolved May 02, 2026, 03:03 PM UTC

1. scheduled Apr 17, 2026, 09:49 PM UTC

   *.uemauth.vmwservices.com domains will be temporarily disabled. This is to ensure customers get multiple chances to detect issues and implement fixes related to the *.uemauth.vmwservices.com domain decommissions. More details can be found here: https://kb.omnissa.com/s/article/6001352 Maintenance Window: Start: Saturday, May 2nd 2026, 14:00 UTC End: Saturday, May 2nd 2026, 15:00 UTC Change: uemauth.vmwservices.com disruption Customer Impact: •Requests to get an OAuth token using any of the decommissioned domains will fail with “connection refused” or “DNS error” System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. scheduled May 02, 2026, 01:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress May 02, 2026, 02:00 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 17, 2026, 09:45 PM UTC· resolved May 22, 2026, 09:31 PM UTC

1. scheduled Apr 17, 2026, 09:45 PM UTC

   *.uemauth.vmwservices.com domains will be decommissioned and replaced with *.uemauth.workspaceone.com domains. More details can be found here: https://kb.omnissa.com/s/article/6001352 Change Date: Tuesday, June 30, 2026 Change: uemauth.vmwservices.com decommission Customer Impact: •Requests to get an OAuth token using any of the decommissioned domains will fail with “connection refused” or “DNS error” System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Apr 16, 2026, 10:47 PM UTC· resolved Jun 02, 2026, 12:01 AM UTC

1. scheduled Apr 16, 2026, 10:47 PM UTC

   Omnissa Intelligence will remove access from the legacy vmwservices.com domain on May 18th, 2026. Only traffic to [region].data.workspaceone.com or [region].data.workspaceone-gov.com will be allowed. If you have not already, please follow the steps outlined in https://kb.omnissa.com/s/article/6000843?lang=en_US&queryTerm=vmwservices.com immediately for all services in use. Impact: - Intelligence API requests to vmwservices.com domains will fail - Attempts to login to intelligence from the vmwservices.com URL will fail - Experience management telemetry data will fail to be sent for agent versions below 25.03 Additional Information and Support: Please visit Service Support Website at Customer Connect (https://customerconnect.omnissa.com/home) to submit a case through Customer Connect. For information on contacting service support, see How to file a Support Request in Customer Connect (https://kb.omnissa.com/s/article/2006985).

2. scheduled May 15, 2026, 05:22 PM UTC

   Removal of access to the legacy vmwservices.com domain has been rescheduled to June 1st, 2026.

3. scheduled Jun 01, 2026, 01:00 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

4. in progress Jun 01, 2026, 02:00 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 15, 2026, 03:35 PM UTC· resolved Apr 20, 2026, 08:09 PM UTC

1. scheduled Apr 15, 2026, 03:35 PM UTC

   Horizon Cloud Service First-Gen is undergoing the weekly scheduled maintenance on the Horizon Cloud Console Access. Maintenance Window: • Start: Wednesday, April 22, 2026, 03:30 UTC • End: Wednesday, April 22, 2026, 06:30 UTC Impact: • There is no impact on end-users and their ability to connect to their desktops. • During this maintenance there will be a brief (not more than 2 minutes) downtime on the Administration Console. Administrative functions will be unavailable or may appear offline during this period. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems. Additional Information and Support: Please visit Service Support Website at Customer Connect (https://customerconnect.omnissa.com/home) to submit a case through Customer Connect. For information on contacting service support, see How to file a Support Request in Customer Connect (https://kb.omnissa.com/s/article/2006985). Thanks for your patience. Additional Information: Omnissa Horizon Cloud Service Team will provide additional updates on our Unified Status page (http://status.workspaceone.com) until the maintenance activity is complete.

Read the full incident report →

Started Apr 13, 2026, 06:09 PM UTC· resolved Apr 25, 2026, 04:29 AM UTC

1. scheduled Apr 13, 2026, 06:09 PM UTC

   Horizon Cloud Service Next-Gen is going to perform Data Center Maintenance in Japan region during the below maintenance window. The Japan Horizon Data Center MQTT service builds will be upgraded. Maintenance Window: • Start: Saturday, April 25, 2026, 02:30 UTC • End: Saturday, April 25, 2026, 05:30 UTC Impact: There is no impact on end-users and their ability to connect to their desktops for Azure and AWS edges. During the maintenance window: • Intermittent failures may occur for the following operations (retries are expected to succeed): • vSphere edges: Ongoing pool provisioning and VM power‑on for new session requests. • Horizon 8 edges: Ongoing cloud‑managed image import, clone, and publish operations. • Universal Broker (Horizon 8 edges): • Session count and session status updates may be temporarily delayed in the Universal Console. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems. Additional Information and Support: Please visit Service Support Website at Customer Connect (https://customerconnect.omnissa.com/home) to submit a case through Customer Connect. For information on contacting service support, see How to file a Support Request in Customer Connect (https://kb.omnissa.com/s/article/2006985). Thanks for your patience. Additional Information: Omnissa Horizon Cloud Service Team will provide additional updates on our Unified Status page (http://status.workspaceone.com) until the maintenance activity is complete.

2. in progress Apr 25, 2026, 02:30 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 13, 2026, 03:46 PM UTC· resolved Apr 21, 2026, 01:34 PM UTC

1. scheduled Apr 13, 2026, 03:46 PM UTC

   Omnissa Connect are performing maintenance on infrastructure in United States. Services will remain accessible during the update with only a few minutes of possibly slower response times and, in some cases, a small number of failed request that are expected to succeed on retry. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. scheduled Apr 21, 2026, 10:30 AM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress Apr 21, 2026, 11:30 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Apr 10, 2026, 02:08 AM UTC· resolved Apr 10, 2026, 02:50 PM UTC

1. resolved Apr 10, 2026, 10:07 AM UTC

   Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

2. investigating Apr 10, 2026, 10:55 AM UTC

   Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 05:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

3. investigating Apr 10, 2026, 11:27 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-04-10 09:00 PDT. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

4. resolved Apr 10, 2026, 03:06 PM UTC

   Description: The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

Read the full incident report →

Started Apr 09, 2026, 02:30 PM UTC· resolved Apr 09, 2026, 03:07 PM UTC

1. investigating Apr 09, 2026, 02:30 PM UTC

   Omnissa Access and Workspace ONE Hub Services is investigating reports of issues with login to access.gc.workspaceone-gov.com. We will provide more information shortly. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. monitoring Apr 09, 2026, 02:31 PM UTC

   Omnissa Access and Workspace ONE Hub Services has completed actions to remediate the issues and confirm that the services are available. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

3. resolved Apr 09, 2026, 03:07 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →

Started Apr 08, 2026, 09:05 PM UTC· resolved Apr 08, 2026, 10:40 PM UTC

1. resolved Apr 08, 2026, 10:22 PM UTC

   Description: Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details Customer symptoms: Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. Workaround: None at this time.

2. resolved Apr 08, 2026, 11:27 PM UTC

   Description: The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. Workaround: None at this time.

Read the full incident report →

Started Apr 08, 2026, 01:30 PM UTC· resolved Apr 08, 2026, 09:40 PM UTC

1. resolved Apr 08, 2026, 06:22 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

2. investigating Apr 08, 2026, 07:02 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 13:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

3. investigating Apr 08, 2026, 08:03 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 15:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

4. investigating Apr 08, 2026, 09:49 PM UTC

   Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning on Wednesday, 2026-04-08 06:30 PDT. Our engineering team has applied the mitigation, and our internal monitoring indicates that delays and errors have subsided. We will continue to monitor for service stability to ensure full recovery. We will provide an update by Wednesday, 2026-04-08 16:00 PDT with current details. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.

5. resolved Apr 08, 2026, 10:54 PM UTC

   Description: The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.

6. resolved Apr 10, 2026, 02:32 AM UTC

   Preliminary Incident Report We apologize for the inconvenience this Gmail service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: Account Suspension: One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. Traffic Blocking: A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

7. resolved Apr 17, 2026, 09:10 AM UTC

   Incident Report Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: External Mail Provider Reachout: Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

Read the full incident report →

Started Mar 20, 2026, 10:30 PM UTC· resolved Mar 21, 2026, 05:03 AM UTC

1. resolved Mar 21, 2026, 03:19 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

2. investigating Mar 21, 2026, 03:46 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

3. investigating Mar 21, 2026, 05:33 AM UTC

   Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation. We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

4. resolved Mar 21, 2026, 07:17 AM UTC

   Description: The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →