Google Outage History
Google partial outage · 1 active incident View live status →Pingoru has recorded 189 incidents for Google: 179 in the last 12 months and 55 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 14 | 282 of 720 (39%) |
| May 2026 | 14 | 655 of 744 (88%) |
| June 2026 | 13 | 560 of 720 (78%) |
| July 2026 | 12 | 560 of 744 (75%) |
| August 2026 | 18 | 519 of 744 (70%) |
| September 2026 | 23 | 391 of 720 (54%) |
| October 2026 | 12 | 285 of 582 (49%) |
Incidents, newest first
Minor October 30, 2025 Google Meet meetings are seeing elevated error rates in upgrading the call on Android. 20h 51m via Google Workspace· Google Meet
Started Oct 30, 2025, 03:05 PM UTC· resolved Oct 31, 2025, 11:56 AM UTC
- monitoring Oct 30, 2025, 04:19 PM UTC
Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures to upgrade the call. Our engineering team has identified the root cause and is working on mitigation. We will provide more information by Thursday, 2025-10-30 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users on Android that upgrade calls to Google Meet meetings are seeing high error rates in upgrading the call Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.
- monitoring Oct 30, 2025, 10:00 PM UTC
Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures to upgrade the call. Our engineering team is actively working on the mitigation efforts. We will provide more information by Thursday, 2025-10-30 16:00 US/Pacific with current details. Symptoms: Users on Android that upgrade calls to Google Meet meetings are seeing high error rates in upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.
- monitoring Oct 30, 2025, 10:50 PM UTC
Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures when upgrading the call. Our engineering team has identified the underlying cause of the issue and a rollback was initiated to mitigate impact. Based on the progress of the rollback, we are observing positive results pertaining to recovery. We expect full mitigation to be completed by Friday, 2025-10-31 12:00 US/Pacific. We will provide more information by Friday, 2025-10-31 12:30 US/Pacific with current details. Symptoms: Users on Android that upgrade calls to Google Meet meetings are observing high error rates when upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.
- resolved Oct 31, 2025, 12:41 PM UTC
Description: The issue with Google Meet has been resolved for all affected customers as of Friday, 2025-10-31 04:56 US/Pacific. From preliminary analysis, the issue was triggered by a recent UI change that made a feature for upgrading calls to Google Meet more prominent for Android users. This led to a surge in usage and revealed an underlying issue with the feature, causing a high failure rate when upgrading calls. Our engineers mitigated the issue by rolling back the UI change. The team will continue to investigate and address the underlying deficiencies in the feature. We thank you for your patience while we worked on resolving the issue. Symptoms: Users on Android that upgrade calls to Google Meet meetings were observing high error rates when upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.
Minor October 25, 2025 AppSheet customers may experience latency issues 1h 55m via Google Workspace· AppSheet
Started Oct 25, 2025, 06:05 AM UTC· resolved Oct 25, 2025, 08:00 AM UTC
- investigating Oct 25, 2025, 07:19 AM UTC
Description: We are experiencing an issue with AppSheet beginning at Friday, 2025-10-24 23:05 PDT. Our engineering team continues to investigate the issue. We will provide an update by Saturday, 2025-10-25 01:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: The impacted customers may experience failures while loading apps or writing data using AppSheet. Workaround: None at this time.
- resolved Oct 25, 2025, 08:24 AM UTC
Description: The issue with AppSheet has been resolved for all affected users as of Saturday, 2025-10-25 01:00 PDT. The issue was triggered due to a maintenance event on a database resulting in lock contention and our engineering mitigated the impact by manually resolving the contention issue. We thank you for your patience while we worked on resolving the issue. Symptoms: The impacted customers might have experienced failures while loading apps or writing data using AppSheet. Workaround: None
- resolved Oct 27, 2025, 04:15 AM UTC
Affected services and features: AppSheet Regions/zones: Global Description: Starting on 24 October 23:05 US/Pacific, AppSheet experienced failures while loading apps or writing data for a duration of 1 hour and 55 minutes. From preliminary analysis, the issue was caused due to a maintenance event on a database resulting in lock contention. Our engineering mitigated the impact by manually resolving the contention issue. Customer impact: The impacted customers might have experienced failures while loading apps or writing data using AppSheet.
Minor October 24, 2025 A subset of customers in EDU domains are experiencing issues accessing Gmail mobile applications. 1d 1h via Google Workspace· Gmail
Started Oct 24, 2025, 05:45 PM UTC· resolved Oct 25, 2025, 07:05 PM UTC
- monitoring Oct 25, 2025, 12:15 AM UTC
Description: We are experiencing an issue with Gmail beginning on Friday, 2025-10-24 10:45 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2025-10-24 20:30 PDT with current details. Symptoms: Affected customers are experiencing issues accessing Gmail mobile applications. Gmail web access is unaffected. Workaround: Customers can access Gmail from the web browser.
- monitoring Oct 25, 2025, 02:55 AM UTC
Description: We are experiencing an issue with Gmail beginning on Friday, 2025-10-24 10:45 PDT. Our engineering team has identified the root cause and implemented mitigation measures. And, currently we are monitoring the status of mitigation. We will provide an update by Monday, 2025-10-27 11:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers may have experienced issues accessing Gmail mobile applications. Gmail web access is unaffected. Workaround: Customers can access Gmail from the web browser.
- monitoring Oct 26, 2025, 02:18 AM UTC
Description: The issue with the GMail is resolved for all the users on Saturday, 2025-10-25 12:05 PDT As per our preliminary analysis, the issue was caused due to a recent code change introduced to OneGoogle for Android and iOS apps. Our engineering team mitigated the issue by rolling back these problematic changes. We apologize to all who are affected by the disruption. We thank you for your patience while we worked on resolving the issue.
- resolved Oct 27, 2025, 11:44 PM UTC
Affected services and features: Gmail - Mobile application users on both ios and android Description: Some Workspace for Education users reported experiencing issues accessing Gmail on their mobile devices. Preliminary analysis indicates that the issue was caused by a recent code change in the UX stack of our first-party mobile applications. Our engineering team mitigated the impact by rolling back the problematic changes. Customer impact: Affected users were unable to access Gmail through mobile applications on Android and iOS devices. Gmail web access was unaffected during the issue.
Minor October 20, 2025 We are investigating an issue impacting Endpoint management for Windows Devices 3d 4h via Google Workspace· Endpoint Management
Started Oct 20, 2025, 07:41 PM UTC· resolved Oct 24, 2025, 12:19 AM UTC
- investigating Oct 20, 2025, 07:50 PM UTC
Description: We are experiencing an issue with Endpoint management beginning on Wednesday, 2025-10-01 00:00 PDT. We detected the impact progressively increasing on Tuesday, 2025-10-14 10:23 PDT. The Windows native settings app responsible for communicating with Google Identity and Endpoint management is using Internet Explorer 11 which has been deprecated by Microsoft. Google Identity servers are failing to serve requests for IE11 which is impacting device enrollment. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-10-20 15:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time
- investigating Oct 20, 2025, 09:41 PM 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 an update by Monday, 2025-10-20 18:30 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- investigating Oct 21, 2025, 01:39 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 an update by Monday, 2025-10-20 20:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- investigating Oct 21, 2025, 02:59 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 an update by Tuesday, 2025-10-21 01:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- investigating Oct 21, 2025, 03:58 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 an update by Tuesday, 2025-10-21 11:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- investigating Oct 21, 2025, 07:17 PM 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 an update by Thursday, 2025-10-23 17:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- investigating Oct 23, 2025, 11:05 PM 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 an update by Friday, 2025-10-24 12:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.
- resolved Oct 24, 2025, 01:04 AM UTC
Description: The issue with Endpoint management for Windows enrollment has been resolved for all affected customers as of Thursday, October 23, 2025, 17:19 PDT. From preliminary analysis, the issue was caused by a browser compatibility problem with the deprecated IE11 used by Microsoft provided Windows Settings app. Our engineers resolved this by deploying a fix to the Google Identity servers to restore support for these requests. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers were not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) were not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None.
- resolved Oct 24, 2025, 06:50 AM UTC
Affected services and features: Endpoint Management Description: Starting on 01 October 2025, Endpoint Management customers experienced the inability to enroll new Windows devices using Windows Settings app or deeplink. We detected the impact when it progressively increased on Tuesday, 2025-10-14 10:23 PDT. From our analysis, the issue originated from a browser compatibility concern. Specifically, the Microsoft-provided Windows Settings application utilized the deprecated Internet Explorer 11, rendering it incompatible with recent modifications to the identity servers. Our engineers resolved this by deploying a fix to the Google Identity servers to restore support for these requests. Customer impact: The Windows native settings application, which facilitates communication with Google Identity and Endpoint management, relies on Internet Explorer 11, a browser no longer supported by Microsoft. Device enrollment was affected due to Google Identity servers unable to fulfill requests from Internet Explorer 11. Customers encountered issues enrolling new Windows devices in Google Endpoint management through the Windows Settings app or deeplink1. However, users leveraging Google Credential Provider for Windows (GCPW) were unaffected by this problem2. Reference(s): 1 Enroll a device in Windows device management (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0%29*%29[https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) 2 Install Google Credential Provider for Windows (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0)
- resolved Oct 27, 2025, 11:10 AM UTC
Incident Report Summary Beginning on 1 October 2025, Google Endpoint Management customers experienced issues enrolling new Windows devices using the native Windows Settings application or direct enrollment deeplinks. This incident started on 1 October 2025 at 00:00 US/Pacific and lasted for 22 days, 17 hours and 19 minutes, with resolution on 23 October 2025 at 17:19 US/Pacific. We sincerely apologize for any impact this disruption had on your device management workflows. We are taking measures to prevent a recurrence. Root Cause The root cause of this incident was a deprecated[1] browser compatibility issue. The device enrollment process initiated from the Windows Settings application relies on an embedded browser component. This component's behavior is based on the now deprecated Internet Explorer 11. Recent updates to Google's Identity servers, intended to enhance security and modernize the platform, inadvertently removed compatibility with the outdated protocols and behaviors exhibited by the Internet Explorer 11 engine. As a result, authentication requests from the Windows Settings enrollment flow could no longer be processed successfully by the updated Identity servers, causing the enrollment to fail. [1] Deprecated browser compatibility issue: https://learn.microsoft.com/en-us/lifecycle/products/internet-explorer-11 Remediation and Prevention The issue was detected on Tuesday, 14 October 2025, at 10:23 US/Pacific, as the impact progressively increased, prompting a detailed investigation. Google engineers traced the failures back to the incompatibility between the Google Identity servers and the enrollment process embedded within the Windows Settings application, which uses a deprecated Internet Explorer 11 component. To remediate the issue, Google engineers developed and deployed a targeted fix to the Google Identity servers. This update restored the servers' ability to handle authentication requests originating from the enrollment flow dependent on the Internet Explorer 11 technology. The rollout of this fix was completed on 23 October 2025 at 17:19 US/Pacific, fully restoring the ability to enroll new Windows devices via the Windows Settings application and deeplinks. Google is committed to preventing similar incidents in the future and is completing the following actions: We are enhancing our testing procedures for Windows device enrollment flows. We are exploring improvements in monitoring to detect issues on lower-traffic enrollment pathways more rapidly. Detailed Description of Impact Google Endpoint Management - From 1 October 2025, 00:00 US/Pacific to 23 October 2025, 17:19 US/Pacific, customers were unable to enroll new Windows devices into Google Endpoint Management when using the built-in Windows Settings application (as described in “Enroll a device” in Windows device management) or an enrollment deeplink. The enrollment process would fail during the authentication phase due to the incompatibility. Customers using the Google Credential Provider for Windows (GCPW) for device setup and login (as described in “Install Google Credential Provider for Windows”) were not affected by this incident and could continue to enroll and manage devices without issue. The impact was limited to the specific enrollment method relying on the Windows Settings interface.
Major October 15, 2025 Incident affecting Studio (Preview) 6h 47m via Firebase· Studio (Preview), Studio (Preview) (global)
Started Oct 15, 2025, 03:14 PM UTC· resolved Oct 15, 2025, 10:01 PM UTC
- resolved Oct 15, 2025, 03:15 PM UTC
Firebase Studio users are experiencing publishing errors when using the "Publish" button.
Major October 9, 2025 Firebase Test Lab is experiencing higher test execution error rate. 1h 18m via Firebase· Test Lab, Test Lab (global)
Started Oct 09, 2025, 10:42 PM UTC· resolved Oct 10, 2025, 12:00 AM UTC
- investigating Oct 09, 2025, 10:45 PM UTC
Firebase Test Lab is experiencing a higher test execution error rate. We currently estimate that. We have temporarily paused the test executions on arm emulators. We are currently investigating the cause.
- resolved Oct 10, 2025, 12:20 AM UTC
Arm emulator test executions have resumed, though at a reduced capacity.
Major October 6, 2025 Some users in asia-east1 could not access environment variables at build time 4d 7h via Firebase· App Hosting, App Hosting (global)
Started Oct 06, 2025, 03:00 PM UTC· resolved Oct 10, 2025, 10:45 PM UTC
- resolved Oct 10, 2025, 11:58 PM UTC
A slow-rolling update to the build system of Firebase App Hosting broke customers' code from being able to see environment variables defined in YAML files. Though the rollout started Monday October 6, we have not correlated this with any customer reports before 8P PST Thursday October 9. The experiment has been rolled back and most customers were never on the experiment path.
Major July 18, 2025 Creating and opening Android Studio workspaces is temporarily unavailable 340d 5h via Firebase· Studio (Preview), Studio (Preview) (global)
Started Jul 18, 2025, 02:00 AM UTC· resolved Jun 23, 2026, 07:00 AM UTC
- investigating Jul 18, 2025, 04:27 PM UTC
Creating and opening Android Studio workspaces is temporarily unavailable
- resolved Jun 24, 2026, 05:05 PM UTC
New workspace creation is disabled in Firebase Studio as of the Sunset Phase 2 launch on June 22, 2026.